CVE-2013-0296 json
Race condition in pigz before 2.2.5 uses permissions derived from the umask when compressing a file before setting that file's permissions…
published 2014-04-27 12 y ago modified 2026-06-16 4 mo ago also EUVD-2013-0316
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Race condition in pigz before 2.2.5 uses permissions derived from the umask when compressing a file before setting that file's permissions to match those of the original file, which might allow local users to bypass intended access permissions while compression is occurring.
Patch / fix
- pigz Debian 14, Debian 13, Debian 12 2.2.4-2
debian advisories DEBIAN-CVE-2013-0296
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-0296 updated cvss 1.9
pigz: Temporary archive representation created with insecure permissions
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
lists.opensuse.org
/opensuse-updates/2013-03/msg00106.html
vendor-advisory
-
mail.zlib.net
/pipermail/pigz-announce_zlib.net/2012-July/000006.html
mailing-list
-
openwall.com
/lists/oss-security/2013/02/16/3
mailing-list
-
openwall.com
/lists/oss-security/2013/02/15/4
mailing-list
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=700608
Sources
- CVE List CVE-2013-0296
- NVD CVE-2013-0296
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.