Bug 2298243 (CVE-2024-39908) - CVE-2024-39908 rexml: DoS vulnerability in REXML
Summary: CVE-2024-39908 rexml: DoS vulnerability in REXML
Keywords:
Status: NEW
Alias: CVE-2024-39908
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2311467
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-16 18:32 UTC by OSIDB Bzimport
Modified: 2024-09-18 19:08 UTC (History)
34 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An uncontrolled resource consumption vulnerability was found in REXML. When parsing an untrusted XML with many specific characters such as `<`, `0`, and `%>`, it can lead to a denial of service.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:6784 0 None None None 2024-09-18 18:54:27 UTC
Red Hat Product Errata RHSA-2024:6785 0 None None None 2024-09-18 19:08:35 UTC

Description OSIDB Bzimport 2024-07-16 18:32:39 UTC
 REXML is an XML toolkit for Ruby. The REXML gem before 3.3.1 has some DoS vulnerabilities when it parses an XML that has many specific characters such as `<`, `0` and `%>`. If you need to parse untrusted XMLs, you many be impacted to these vulnerabilities. The REXML gem 3.3.2 or later include the patches to fix these vulnerabilities. Users are advised to upgrade. Users unable to upgrade should avoid parsing untrusted XML strings.

Comment 1 errata-xmlrpc 2024-09-18 18:54:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:6784 https://access.redhat.com/errata/RHSA-2024:6784

Comment 2 errata-xmlrpc 2024-09-18 19:08:33 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:6785 https://access.redhat.com/errata/RHSA-2024:6785


Note You need to log in before you can comment on or make changes to this bug.