CVE-2005-2541
NoneCVSS
—
EPSS
4.0%
Published
Aug 10, 2005
CISA due date
—
Cloudanix analysis
An old file-extraction tool can silently install programs that run with extra permissions, letting attackers gain more control over a system than intended.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Privilege Gain
- Component
- Application
- Class
- Improper Input Validation
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Tar extraction fails to warn on setuid or setgid files inside archives, allowing the files to be written with their original permissions and potentially executed with elevated privileges.
Why it matters to the business
Systems using the listed Chainguard cert-manager packages face a long-known risk of local or remote privilege escalation when extracting untrusted archives; the flaw is more than twenty years old with negligible current exploitation likelihood and no ransomware usage.
How an attack unfolds
An attacker creates a tar archive containing a setuid binary, delivers it to a target system (via download, email, or supply-chain), and relies on the victim extracting it with tar; because no warning is shown, the setuid file is installed and can later be executed to gain the file owner's privileges.
How to fix it
Upgrade each affected package to the stated fixed version: cert-manager-fips-1.14 (Chainguard) to 1.14.7-r1, cert-manager-fips-1.14-acmesolver (Chainguard) to 1.14.7-r1, cert-manager-fips-1.14-cainjector (Chainguard) to 1.14.7-r1, cert-manager-fips-1.14-controller (Chainguard) to 1.14.7-r1, cert-manager-fips-1.14-webhook (Chainguard) to 1.14.7-r1, cmctl-1.14-fips (Chainguard) to 1.14.7-r1, and cert-manager-fips-1.14-startupapicheck (Chainguard) to 1.14.7-r1.
How to confirm the fix worked
Verify installed package versions match or exceed the listed fixed releases and confirm tar behavior now emits warnings for setuid/setgid files during extraction.
Typical attack path
- Create tar archive containing a setuid or setgid executable
- Deliver the archive to the target environment
- Victim extracts the archive without any setuid warning
- Malicious file is written with elevated permissions
- Attacker later executes the file to obtain higher privileges
How to detect it
Examine system logs and file-creation events for unexpected setuid or setgid binaries appearing after tar extractions; because the issue is decades old and not known to be actively exploited, focus on historical forensic review of package-change and file-permission audit trails.
What your security team should do
- Immediately update all listed Chainguard packages to the 1.14.7-r1 releases
- Scan container images for any remaining vulnerable tar versions
- Add policy checks that block extraction of archives containing setuid/setgid entries
- Review and harden any automated archive-extraction workflows
The record
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.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:10 | tar | 0 | No fix |
| Debian:11 | tar | 0 | No fix |
| Debian:12 | tar | 0 | No fix |
| Debian:13 | tar | 0 | No fix |
Related vulnerabilities
- CVE-2023-39804 In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an… Also affects tar
- CVE-2010-0624 Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client… Also affects tar
- CVE-2007-4476 Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack… Also affects tar
- CVE-2006-6097 GNU tar 1.16 and 1.15.1, and possibly other versions, allows user-assisted attackers to… Also affects tar
- CVE-2025-45582 GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR… Also affects tar
- CVE-2016-6321 Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14… Also affects tar