CVE-2024-41123 (Medium) detected in rexml-3.2.8.gem

[mend-bolt-for-github]

CVE-2024-41123 - Medium Severity Vulnerability

Vulnerable Library - rexml-3.2.8.gem

An XML toolkit for Ruby

Library home page: https://rubygems.org/gems/rexml-3.2.8.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /home/wss-scanner/.gem/ruby/3.2.0/cache/rexml-3.2.8.gem

Dependency Hierarchy:

• jekyll-4.3.3.gem (Root Library)
  • kramdown-2.4.0.gem
    • ❌ rexml-3.2.8.gem (Vulnerable Library)

Found in base branch: master

Vulnerability Details

REXML is an XML toolkit for Ruby. The REXML gem before 3.3.2 has some DoS vulnerabilities when it parses an XML that has many specific characters such as whitespace character, >] and ]>. The REXML gem 3.3.3 or later include the patches to fix these vulnerabilities.

Publish Date: 2024-08-01

URL: CVE-2024-41123

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-r55c-59qm-vjw6

Release Date: 2024-08-01

Fix Resolution: rexml - 3.3.3

---

Step up your Open Source Security Game with Mend here

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.