How severe is CVE-2005-2541?

CVE-2005-2541 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2005-2541 being actively exploited?

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

What products are affected by CVE-2005-2541?

CVE-2005-2541 affects Gnu Tar. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2005-2541?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2005-2541 published?

CVE-2005-2541 was published on 2005-08-10 and last updated on 2026-06-16.

CVE-2005-2541

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

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (89th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gnu Tar
Published: 2005-08-10
Last modified: 2026-06-16

Description

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Frequently asked questions

What is CVE-2005-2541?: Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.
How severe is CVE-2005-2541?: CVE-2005-2541 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2005-2541 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2541?: CVE-2005-2541 affects Gnu Tar. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2005-2541?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2005-2541 published?: CVE-2005-2541 was published on 2005-08-10 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:gnu:tar:1.15.1:*:*:*:*:*:*:*

More vulnerabilities in Gnu Tar

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…
CVE-2023-39804 — Medium (CVSS 6.2): In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

All CVEs affecting Gnu Tar →