Skip to content

GHSA-vg3r-rm7w-2xgh CVE-2024-35176

REXML contains a denial of service vulnerability

Medium RubyGems
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
2.06%
Chance of exploitation in the next 30 days. Higher than 81.36% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
Fix
3.2.7
Upgrade rexml to this version or later

Description

Impact

The REXML gem before 3.2.6 has a DoS vulnerability when it parses an XML that has many >s in an attribute value.

If you need to parse untrusted XMLs, you may be impacted to this vulnerability.

Patches

The REXML gem 3.2.7 or later include the patch to fix this vulnerability.

Workarounds

Don't parse untrusted XMLs.

References

Affected versions

RubyGems

PackageVulnerableFixed in
rexml
< 3.2.7
3.2.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

rexml RubyGems → 3.2.7

bundler
bundle update rexml # Gemfile: gem "rexml", ">= 3.2.7"

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-r55c-59qm-vjw6
REXML DoS vulnerability
High Linked by the source
GHSA-c2f4-jgmc-q2r5
REXML has DoS condition when parsing malformed XML file
Medium Also affects rexml
GHSA-2rxp-v6pw-ch6m
REXML ReDoS vulnerability
High Also affects rexml
GHSA-vmwr-mc7x-5vc3
REXML denial of service vulnerability
Medium Also affects rexml
GHSA-5866-49gr-22v4
REXML DoS vulnerability
High Also affects rexml
GHSA-4xqq-m2hx-25v8
REXML denial of service vulnerability
Medium Also affects rexml
GHSA-8cr8-4vfw-mr7h
REXML round-trip instability
High Also affects rexml
GHSA-cggf-277g-3q54
pypdf has possible large memory usage when parsing page tree
High Same weakness, CWE-400
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor