How severe is CVE-2006-0300?

CVE-2006-0300 has a CVSS 2.0 base score of 5.1, rated medium severity.

Is CVE-2006-0300 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-0300?

CVE-2006-0300 primarily affects Gnu Tar. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-0300?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2006-0300 published?

CVE-2006-0300 was published on 2006-02-24 and last updated on 2026-06-16.

CVE-2006-0300

CVE-2006-0300 is a medium-severity vulnerability in Gnu Tar with a CVSS 2.0 base score of 5.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.1)
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gnu Tar
Published: 2006-02-24
Last modified: 2026-06-16

Description

Buffer overflow in tar 1.14 through 1.15.90 allows user-assisted attackers to cause a denial of service (application crash) and possibly execute code via unspecified vectors involving PAX extended headers.

Frequently asked questions

What is CVE-2006-0300?: Buffer overflow in tar 1.14 through 1.15.90 allows user-assisted attackers to cause a denial of service (application crash) and possibly execute code via unspecified vectors involving PAX extended headers.
How severe is CVE-2006-0300?: CVE-2006-0300 has a CVSS 2.0 base score of 5.1, rated medium severity.
Is CVE-2006-0300 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-0300?: CVE-2006-0300 primarily affects Gnu Tar. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-0300?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2006-0300 published?: CVE-2006-0300 was published on 2006-02-24 and last updated on 2026-06-16.

References

Affected products (5)

cpe:2.3:a:gnu:tar:1.14:*:*:*:*:*:*:*
cpe:2.3:a:gnu:tar:1.14.1:*:*:*:*:*:*:*
cpe:2.3:a:gnu:tar:1.15:*:*:*:*:*:*:*
cpe:2.3:a:gnu:tar:1.15.1:*:*:*:*:*:*:*
cpe:2.3:a:gnu:tar:1.15.90:*:*:*:*:*:*:*

More vulnerabilities in Gnu Tar

CVE-2005-2541 — Critical (CVSS 10.0): Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or…
CVE-2019-9923 — High (CVSS 7.5): pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that…
CVE-2016-6321 — High (CVSS 7.5): Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might allow remote…
CVE-2007-4476 — High (CVSS 7.5): Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a…
CVE-2010-0624 — Medium (CVSS 6.8): Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar…
CVE-2007-4131 — Medium (CVSS 6.8): Directory traversal vulnerability in the contains_dot_dot function in src/names.c in GNU tar allows user-assisted…

All CVEs affecting Gnu Tar →