Skip to content

Directory traversal in convert-svg-core

High severity GitHub Reviewed Published Jun 11, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

npm convert-svg-core (npm)

Affected versions

< 0.6.4

Patched versions

0.6.4

Description

The package convert-svg-core before 0.6.4 is vulnerable to Directory Traversal due to improper sanitization of SVG tags. Exploiting this vulnerability is possible by using a specially crafted SVG file.

References

Published by the National Vulnerability Database Jun 10, 2022
Published to the GitHub Advisory Database Jun 11, 2022
Reviewed Jun 17, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.182%
(56th percentile)

Weaknesses

CVE ID

CVE-2022-24278

GHSA ID

GHSA-5f47-rcg5-9m24

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.