🚨 [security] Update rexml 3.3.2 → 3.3.6 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ rexml (indirect, 3.3.2 → 3.3.6) · Repo · Changelog

Security Advisories 🚨

🚨 REXML denial of service vulnerability

Impact

The REXML gem before 3.3.6 has a DoS vulnerability when it parses an XML that has many deep elements that have same local name attributes.

If you need to parse untrusted XMLs with tree parser API like REXML::Document.new, you may be impacted to this vulnerability. If you use other parser APIs such as stream parser API and SAX2 parser API, this vulnerability is not affected.

Patches

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

Workarounds

Don't parse untrusted XMLs with tree parser API.

🚨 REXML DoS vulnerability

Impact

The REXML gem before 3.3.2 has a DoS vulnerability when it parses an XML that has many entity expansions with SAX2 or pull parser API.

If you need to parse untrusted XMLs with SAX2 or pull parser API, you may be impacted to this vulnerability.

Patches

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

Workarounds

Don't parse untrusted XMLs with SAX2 or pull parser API.

References

• https://www.ruby-lang.org/en/news/2008/08/23/dos-vulnerability-in-rexml/ : This is a similar vulnerability
• https://www.ruby-lang.org/en/news/2024/08/01/dos-rexml-cve-2024-41946/: An announce on www.ruby-lang.org

🚨 REXML DoS vulnerability

Impact

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 ]>.

If you need to parse untrusted XMLs, you may be impacted to these vulnerabilities.

Patches

The REXML gem 3.3.3 or later include the patches to fix these vulnerabilities.

Workarounds

Don't parse untrusted XMLs.

References

• GHSA-vg3r-rm7w-2xgh : This is a similar vulnerability
• GHSA-4xqq-m2hx-25v8 : This is a similar vulnerability
• https://www.ruby-lang.org/en/news/2024/08/01/dos-rexml-cve-2024-41123/: An announce on www.ruby-lang.org

Release Notes

3.3.6

Improvements

• Removed duplicated entity expansions for performance.

  • GH-194
  • Patch by Viktor Ivarsson.

• Improved namespace conflicted attribute check performance. It was
  too slow for deep elements.

  • Reported by l33thaxor.

Fixes

• Fixed a bug that default entity expansions are counted for
  security check. Default entity expansions should not be counted
  because they don't have a security risk.

  • GH-198
  • GH-199
  • Patch Viktor Ivarsson

• Fixed a parser bug that parameter entity references in internal
  subsets are expanded. It's not allowed in the XML specification.

  • GH-191
  • Patch by NAITOH Jun.

• Fixed a stream parser bug that user-defined entity references in
  text aren't expanded.

  • GH-200
  • Patch by NAITOH Jun.

Thanks

• Viktor Ivarsson

• NAITOH Jun

• l33thaxor

3.3.5

Fixes

• Fixed a bug that REXML::Security.entity_expansion_text_limit
  check has wrong text size calculation in SAX and pull parsers.
  • GH-193
  • GH-195
  • Reported by Viktor Ivarsson.
  • Patch by NAITOH Jun.

Thanks

• Viktor Ivarsson

• NAITOH Jun

3.3.4

Fixes

• Fixed a bug that REXML::Security isn't defined when
  REXML::Parsers::StreamParser is used and
  rexml/parsers/streamparser is only required.
  • GH-189
  • Patch by takuya kodama.

Thanks

• takuya kodama

3.3.3

Improvements

• Added support for detecting invalid XML that has unsupported
  content before root element

  • GH-184
  • Patch by NAITOH Jun.

• Added support for REXML::Security.entity_expansion_limit= and
  REXML::Security.entity_expansion_text_limit= in SAX2 and pull
  parsers

  • GH-187
  • Patch by NAITOH Jun.

• Added more tests for invalid XMLs.

  • GH-183
  • Patch by Watson.

• Added more performance tests.

  • Patch by Watson.

• Improved parse performance.

  • GH-186
  • Patch by tomoya ishida.

Thanks

• NAITOH Jun

• Watson

• tomoya ishida

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 42 commits:

• Add 3.3.6 entry
• parser tree: improve namespace conflicted attribute check performance
• Fix a bug that Stream parser doesn't expand the user-defined entity references for "text" (#200)
• parser: keep the current namespaces instead of stack of Set
• parser: move duplicated end tag check to BaseParser
• test tree-parser: move common method to base class
• test: fix indent
• test: fix indent
• Use loop instead of recursive call for Element#namespace
• Use loop instead of recursive call for Element#root
• test: split duplicated attribute case and namespace conflict case
• Fix to not allow parameter entity references at internal subsets (#191)
• Fix RuntimeError in `REXML::Parsers::BaseParser` for valid feeds (#199)
• Improve `BaseParser#unnormalize` (#194)
• Bump version
• Add 3.3.5 entry
• Fix calculation of Security.entity_expansion_text_limit in SAX/pull parsers (#195)
• Bump version
• Add 3.3.4 entry
• Add missing rexml/security require in rexml/parsers/baseparser.rb (#189)
• Bump version
• Add 3.3.3 entry
• test: add a performance test for attribute list declaration
• test: fix wrong test name
• test: use double quote for string literal
• test: don't use abbreviated name
• test: add a performance test for PI with many tabs
• parse pi: improve invalid case detection
• test: fix a typo
• test: use double quote for string literal
• test: add performance tests for entity declaration
• test: use double quote for string literal
• test: add a performance test for %...; in document declaration
• test: use double quote for string literal
• test: fix location
• Fix source.match performance without specifying term string (#186)
• Add support for XML entity expansion limitation in SAX and pull parsers (#187)
• Add more invalid test cases for parsing entitly declaration (#183)
• Add support for detecting invalid XML that has unsupported content before root element (#184)
• Fix method scope in test in order to invoke the tests properly and fix exception message (#182)
• Add missing references in 3.3.2 entry
• Bump version

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.26%. Comparing base (f7c75c9) to head (bafac67).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   89.26%   89.26%           
=======================================
  Files           8        8           
  Lines         298      298           
  Branches      104      104           
=======================================
  Hits          266      266           
  Misses         32       32           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.