Security Digest · Vulnerability record

CVE-2024-34391: libxmljs vulnerable to type confusion when parsing specially crafted XML

libxmljs is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking a function on the result of attrs() that was called on a parsed node.

CVSS 9.2 Critical EPSS 1.1% · p65

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 1.1%, percentile 65: FIRST’s model estimates a 1.1% chance of exploitation activity in the next 30 days, higher than 65% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes libxmljs (npm) <= 1.0.11, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

libxmljs is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking a function on the result of attrs() that was called on a parsed node. This vulnerability might lead to denial of service (on both 32-bit systems and 64-bit systems), data leak, infinite loop and remote code execution (on 32-bit systems with the XMLPARSEHUGE flag enabled).

From the GitHub advisory

libxmljs is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking a function on the result of attrs() that was called on a parsed node. This vulnerability might lead to denial of service (on both 32-bit systems and 64-bit systems), data leak, infinite loop and remote code execution (on 32-bit systems with the XMLPARSEHUGE flag enabled).

Weakness type: CWE-843.

Product: libxmljs (npm) · Assigned by: JFROG · Published: 2024-05-02

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npmlibxmljs<= 1.0.11none listed
VendorProductAffected versions (per CVE record)
libxmljs<= 1.0.11

Severity scores

Scored byCVSSScoreVector
JFROG3.18.1 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: present (depends on deployment conditions)
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 1.10% probability of exploitation activity in the next 30 days; percentile 65.

Timeline

  • — CVE record published by JFROG
  • — GitHub-reviewed advisory GHSA-6433-x5p4-8jc7 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-6433-x5p4-8jc7 github.com
  2. CVE.org record CVE-2024-34391 cve.org
  3. NVD entry CVE-2024-34391 nvd.nist.gov

Other references from the CVE record and advisory

  1. research.jfrog.com research.jfrog.com
  2. github.com github.com

Critical npm advisories · Today’s Security Digest