Security readout for executives and security teams
Plain-English summary
SharpCompress versions before 0.21.0 could extract a malicious Zip entry outside the intended folder. In practical terms, an attacker who can supply an archive to an affected application may overwrite files the application can write. Business impact depends on where extraction runs and file permissions.
Executive priority
Prioritize remediation where archive upload or ingestion is internet-facing or handles third-party files. The issue can become serious because arbitrary file writes may affect configuration, application code, or data integrity.
Technical view
This is a CWE-22 directory traversal issue in SharpCompress archive extraction, also known as Zip Slip. The CVE states that ../ sequences in Zip archive entries were mishandled, allowing arbitrary file writes during extraction. The public record names SharpCompress before 0.21.0 as affected.
Likely exposure
Exposure is most likely in .NET applications using SharpCompress before 0.21.0 to extract Zip archives supplied by users, partners, integrations, or automated ingestion pipelines.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires an affected extraction path and attacker-controlled archive content, with impact constrained by the process write permissions and deployment layout.
Researcher notes
Evidence is strong for affected component and vulnerability class, but the bundle lacks CVSS, exploit prevalence, and detailed environmental prerequisites. Validate reachability in the application’s archive handling rather than treating dependency presence alone as full exposure.
Mitigation direction
- Upgrade SharpCompress to version 0.21.0 or later.
- Avoid extracting untrusted archives until the dependency is upgraded.
- Run archive extraction with least-privilege filesystem permissions.
- Review the upstream PR and commit before relying on workarounds.
Validation and detection
- Inventory applications for SharpCompress versions below 0.21.0.
- Find workflows that extract Zip archives from external sources.
- Confirm deployed artifacts use the fixed dependency version.
- Review extraction destinations for sensitive writable paths.
- Check dependency scanning results for SNYK-DOTNET-SHARPCOMPRESS-60246.
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-1002206 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://snyk.io/vuln/SNYK-DOTNET-SHARPCOMPRESS-60246CVE reference · x_refsource_MISC
- https://github.com/snyk/zip-slip-vulnerabilityCVE reference · x_refsource_MISC
- https://github.com/adamhathcock/sharpcompress/pull/374CVE reference · x_refsource_CONFIRM
- https://github.com/adamhathcock/sharpcompress/commit/42b1205fb435de523e6ef8ac5b7bafbe712997f6CVE reference · x_refsource_CONFIRM
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.