mapshaper is vulnerable to Path Traversal
61
Medium Risk
The export path in mapshaper uses a layer's name directly as the output file basename in assignUniqueLayerNames. Because layer names are derived from input data (for example a TopoJSON object key), a crafted input file can supply a name containing path separators, a NULL byte, or a Windows drive prefix, causing output files to be written outside the intended output directory. This allows arbitrary file write or overwrite when a victim converts an untrusted file. The fix rejects layer names that resolve to unsafe filenames before any file is written.
You are affected if you are using a version that falls within the vulnerable range.
mapshaper is vulnerable to Path Traversal in versions 0.1.3 - 0.7.26.
Upgrade the mapshaper library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant