[GHSA-mg49-jqgw-gcj6] libxmljs vulnerable to type confusion when parsing specially crafted XML #5725
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.
Updates
Comments
Based on the provided advisory details and analysis of CVE-2024-34392, here are the recommended improvements with supporting evidence:
Suggested Improvements
Patched Version Field
e.g. 1.2.3
1.0.12
Description Enhancement
"libxmljs is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking the
namespaces()
function...""libxmljs suffers from a type confusion vulnerability when parsing malicious XML content. Triggered by invoking the
namespaces()
function on a grand-child node of an entity reference, this flaw occurs due to improper handling of namespace definitions in_wrap__xmlNode_nsDef_get()
. Successful exploitation allows memory corruption, leading to denial of service or remote code execution."_wrap__xmlNode_nsDef_get()
).References
Severity Justification
"Critical severity (CVSS 9.3) reflects: (1) Network-based exploitation without user interaction, (2) Full system compromise via RCE, (3) No privileges required."
Summary of Changes
1.0.12
(added)Reason for Change
This improvement set ensures accuracy, provides actionable mitigation (upgrade to
1.0.12
), and maintains compliance with GitHub's advisory standards. The changes will be submitted as a pull request for curator review.