Security readout for executives and security teams
Plain-English summary
SharpCompress before 0.29.0 can write an extracted archive file just outside the intended directory in some configurations. The impact is limited arbitrary file creation, not full system takeover. Risk is highest where applications extract user-supplied archives using full path extraction.
Executive priority
Treat as a moderate-priority dependency remediation. It is not presented as actively exploited, but archive extraction bugs can become business-relevant when exposed to customer uploads or automated ingestion pipelines.
Technical view
The flaw is a CWE-22 partial path traversal in archive extraction. When ExtractFullPath is true, the prefix check did not require a trailing slash on the destination path, allowing similarly prefixed sibling paths. CVSS is 4.3 with low integrity impact and low privileges required.
Likely exposure
Exposure is limited to applications using SharpCompress versions before 0.29.0, especially code paths that extract archives with ExtractFullPath enabled. Systems not using SharpCompress, not extracting archives, or already on 0.29.0 or later are not indicated as affected by the bundle.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation depends on an attacker being able to influence archive contents and trigger extraction in an affected application. The advisory describes limited arbitrary file creation constrained by destination and filename conditions.
Researcher notes
Focus review on SharpCompress extraction call sites, destination path normalization, and whether sibling-path writes could affect meaningful application files. The public bundle names the fix version but gives no broader affected product list beyond SharpCompress.
Mitigation direction
- Upgrade SharpCompress to version 0.29.0 or later.
- Review vendor advisory and release notes for application-specific guidance.
- Disable full path extraction where it is not required.
- Restrict archive extraction to trusted inputs when possible.
- Add extraction path containment checks around affected workflows.
Validation and detection
- Inventory .NET projects and lockfiles for SharpCompress versions before 0.29.0.
- Identify archive extraction paths that enable ExtractFullPath or WriteEntryToDirectory.
- Confirm whether untrusted or low-privileged users can submit archives.
- Verify upgraded builds resolve SharpCompress to 0.29.0 or later.
- Use safe internal tests to confirm extracted files stay inside the destination directory.
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-2021-39208 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/adamhathcock/sharpcompress/security/advisories/GHSA-jp7f-grcv-6mjfCVE reference · x_refsource_CONFIRM
- https://github.com/adamhathcock/sharpcompress/pull/614CVE reference · x_refsource_MISC
- https://github.com/adamhathcock/sharpcompress/releases/tag/0.29.0CVE 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.
