Security readout for executives and security teams
Plain-English summary
This CVE affects the Go mholt/archiver package. When extracting a crafted archive, vulnerable versions could write files outside the intended destination, potentially overwriting application or system files. Business risk depends on whether systems accept and extract untrusted archives. Sources do not provide CVSS, confirmed active exploitation, or a named release version.
Executive priority
Treat as a targeted remediation item where the package processes untrusted archives. It is not KEV-listed in the provided data, but arbitrary file write can become high-impact if extraction occurs in privileged or production paths.
Technical view
CWE-22 directory traversal in mholt/archiver before commit e4ef56d48eb029648b0e895bb0b6a393ef0829c3. Archive entry paths were mishandled during extraction, enabling Zip Slip style arbitrary file writes outside the extraction directory. The source bundle identifies the fix commit and pull request, but not an affected version range beyond before that commit.
Likely exposure
Exposure is most likely in Go applications, CLIs, or services that depend on mholt/archiver and extract archives from users, partners, uploads, build artifacts, or other untrusted sources. Systems that only extract trusted internal archives have lower practical exposure.
Exploitation context
The public sources describe the vulnerability class and affected package, but the bundle marks KEV false and provides no cited evidence of active exploitation. Exploitation would require a malicious archive being processed by a vulnerable extractor in a context where file overwrite has impact.
Researcher notes
The evidence supports Zip Slip directory traversal and arbitrary file write in mholt/archiver before the named commit. Severity metadata is incomplete: no CVSS is supplied, no precise version range is listed, and no active exploitation evidence is provided in the bundle.
Mitigation direction
- Upgrade mholt/archiver to code containing commit e4ef56d48eb029648b0e895bb0b6a393ef0829c3.
- Check current vendor or project guidance for the maintained replacement version.
- Avoid extracting untrusted archives with vulnerable builds until remediated.
- Restrict extraction privileges and destination write permissions where practical.
- Review applications for archive extraction paths reachable by external users.
Validation and detection
- Inventory Go modules and binaries for mholt/archiver usage.
- Confirm the deployed dependency includes the referenced fix commit or later code.
- Identify routes, jobs, or tools that extract user-supplied archives.
- Review tests for traversal-safe extraction behavior without using offensive payload detail.
- Prioritize validation on internet-facing or partner-facing upload workflows.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1002207 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://snyk.io/research/zip-slip-vulnerabilityCVE reference · x_refsource_MISC
- https://github.com/snyk/zip-slip-vulnerabilityCVE reference · x_refsource_MISC
- https://github.com/mholt/archiver/pull/65CVE reference · x_refsource_CONFIRM
- https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3CVE reference · x_refsource_CONFIRM
- https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARCHIVER-50071CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.