libxmljs-1.0.11.tgz: 1 vulnerabilities (highest severity is: 9.3)

[mend-for-github-com[bot]]

Vulnerable Library - libxmljs-1.0.11.tgz

Library home page: https://registry.npmjs.org/libxmljs/-/libxmljs-1.0.11.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/libxmljs/package.json

Found in HEAD commit: 141277bbe1dbdc1d667de53b0177a226b25277eb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (libxmljs version)	Remediation Possible**
CVE-2024-34392	Critical	9.3	libxmljs-1.0.11.tgz	Direct	N/A	❌

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-34392

### Vulnerable Library - libxmljs-1.0.11.tgz

Library home page: https://registry.npmjs.org/libxmljs/-/libxmljs-1.0.11.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/libxmljs/package.json

Dependency Hierarchy: - :x: **libxmljs-1.0.11.tgz** (Vulnerable Library)

Found in HEAD commit: 141277bbe1dbdc1d667de53b0177a226b25277eb

Found in base branch: master

### Vulnerability Details

libxmljs is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking the namespaces() function (which invokes _wrap__xmlNode_nsDef_get()) on a grand-child of a node that refers to an entity. This vulnerability can lead to denial of service and remote code execution.

Publish Date: 2024-05-02

URL: CVE-2024-34392

### CVSS 4 Score Details (9.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS4 Scores, click here.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be closed automatically in one week if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.