CVE Intelligence
Medium Denial of service exploit reference

CVE-2018-20482 — GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which...

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root).

Published Dec 26, 2018 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.5% (30-day exploitation probability)+7
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.53%
ahead of 43% of scored CVEs · Oct 14, 2026
Affects
Debian
Debian Linux and 2 more
CVSS base
4.7
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Gnu Tar, Opensuse Leap).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 8.0version 9.0 Vulnerable NIST National Vulnerability Database
Gnu Tar ≤ 1.30 Vulnerable NIST National Vulnerability Database
Opensuse Leap version 15.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.7 CVSS 3.1 Medium 1.0 3.6 nvd@nist.gov via NIST National Vulnerability Database
4.7 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
1.9 CVSS 2.0 Low 3.4 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-835 · Infinite Loop

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.53%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Track CPU/memory spikes and availability drops correlated with request patterns.
endpoint telemetry (EDR)resource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · gnu/tar, debian/debian linux, opensuse/leap
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 4.7
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2018
  • CVE published
    Dec 26, 2018 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

13 on the record

Elsewhere on this site

Debian
every CVE for this vendor
CWE-835
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-18477 TOCTOU Race Condition in Gnu Tar Aug 3, 2026
  • Medium CVE-2026-18508 Link Following in Gnu Tar Aug 3, 2026
  • High CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • Medium CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD Jul 3, 2026
  • Medium CVE-2026-56968 Use of Uninitialized Resource in Gnu Sasl Jun 23, 2026
  • High CVE-2026-49975 Apache HTTP Server: mod_http2 denial of service Jun 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-20482 is "GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which...", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.53% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.