π¨ [security] Update nokogiri 1.10.1 β 1.16.5 (minor) #241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π¨ 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?
Security Advisories π¨
π¨ Nokogiri updates packaged libxml2 to v2.12.7 to resolve CVE-2024-34459
π¨ Nokogiri updates packaged libxml2 to v2.12.7 to resolve CVE-2024-34459
π¨ Use-after-free in libxml2 via Nokogiri::XML::Reader
π¨ Use-after-free in libxml2 via Nokogiri::XML::Reader
π¨ Nokogiri update packaged libxml2 to v2.12.5 to resolve CVE-2024-25062
π¨ Nokogiri update packaged libxml2 to v2.12.5 to resolve CVE-2024-25062
π¨ Nokogiri updates packaged libxml2 to v2.10.4 to resolve multiple CVEs
π¨ Unchecked return value from xmlTextReaderExpand
π¨ Update bundled libxml2 to v2.10.3 to resolve multiple CVEs
π¨ Nokogiri Implements libxml2 version vulnerable to null pointer dereferencing
π¨ Nokogiri implementation of libxslt vulnerable to heap corruption
π¨ Nokogiri affected by libxslt Use of Uninitialized Resource/Use After Free vulnerability
π¨ libxslt Type Confusion vulnerability that affects Nokogiri
π¨ Nokogiri has vulnerable dependencies on libxml2 and libxslt
π¨ Uninitialized read in Nokogiri gem
π¨ Nokogiri contains libxml Out-of-bounds Write vulnerability
π¨ Nokogiri Implements libxml2 version vulnerable to use-after-free
π¨ Nokogiri Improperly Handles Unexpected Data Type
π¨ Integer Overflow or Wraparound in libxml2 affects Nokogiri
π¨ Nokogiri vulnerable to libxslt protection mechanism bypass
π¨ Out-of-bounds Write in zlib affects Nokogiri
π¨ Nokogiri Inefficient Regular Expression Complexity
π¨ XML Injection in Xerces Java affects Nokogiri
π¨ Denial of Service (DoS) in Nokogiri on JRuby
π¨ Nokogiri affected by zlib's Out-of-bounds Write vulnerability
π¨ Vulnerable dependencies in Nokogiri
π¨ Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby
π¨ Nokogiri updates packaged dependency on libxml2 from 2.9.10 to 2.9.12
π¨ Nokogiri::XML::Schema trusts input by default, exposing risk of XXE vulnerability
π¨ libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation
π¨ Nokogiri Command Injection Vulnerability
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
π racc (added, 1.7.3)
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