CVE-2024-34394 json
libxmljs2 namespaces type confusion RCE
published 2y ago modified last mo. also GHSA-78h3-pg4x-j8cv , EUVD-2024-1484
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
libxmljs2 is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking the namespaces() function (which invokes XmlNode::get_local_namespaces()) on a grand-child of a node that refers to an entity. This vulnerability can lead to denial of service and remote code execution.
Is CVE-2024-34394 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | libxmljs2 | <=0.35.0 |
no fix listed |
Affected products
- marudor libxmljs2
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
- research.jfrog.com /vulnerabilities/libxmljs2-namespaces-type-confusion-rce-jfsa-2024-001034098/
-
github.com
/marudor/libxmljs2/issues/205
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-34394
advisory
-
github.com
/marudor/libxmljs2
package
-
research.jfrog.com
/vulnerabilities/libxmljs2-namespaces-type-confusion-rce-jfsa-2024-001034098
web
Sources
- CVE List CVE-2024-34394
- GitHub Advisory GHSA-78h3-pg4x-j8cv
- NVD CVE-2024-34394
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.