Skip to content

Path Traversal in mcstatic

High severity GitHub Reviewed Published Jul 27, 2018 to the GitHub Advisory Database • Updated Jan 31, 2023

Package

npm mcstatic (npm)

Affected versions

<= 0.0.20

Patched versions

None

Description

All versions of mcstatic are vulnerable to path traversal.

Recommendation

No fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.

References

Published by the National Vulnerability Database Jun 7, 2018
Published to the GitHub Advisory Database Jul 27, 2018
Reviewed Jun 16, 2020
Last updated Jan 31, 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.449%
(76th percentile)

Weaknesses

CVE ID

CVE-2018-3730

GHSA ID

GHSA-3r8f-gphx-9m2c

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.