LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35517: Apache Commons Compress 1.1 to 1.20 denial of service vulnerability

When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' tar package.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A small malicious TAR archive can make vulnerable Apache Commons Compress versions consume excessive memory until the Java process runs out of memory. The likely business impact is service disruption where applications accept or process TAR files from users, partners, or automated feeds. Exposure is most likely in Java applications that use Apache Commons Compress to parse TAR files, especially upload, extraction, scanning, backup, build, or ingestion workflows. Transitive dependencies should be checked because downstream Apache project threads reference upgrades to commons-compress 1.21. Treat this as a targeted availability risk, not a data theft issue based on current sources. Prioritize internet-facing or business-critical services that process uploaded TAR archives, then address internal tooling and transitive dependencies. Mitigation focus: Upgrade Apache Commons Compress beyond affected 1.1 through 1.20, following Apache guidance.; Check dependency trees for transitive commons-compress versions.; Restrict untrusted TAR processing where upgrades are delayed..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-130: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2021-35517 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
21Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Commons Compress1.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-130 · source CWE mapping

Improper Handling of Length Parameter Inconsistency

Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.