CVE-2023-42503
CVE-2023-42503 · Apache Commons Compress: Denial of service via CPU consumption for malformed TAR file
CVSS 5.5 · Medium · EPSS 0.6% · Fix available
Compare with your installed version
Affected products and known fixed versions are public information. Compare them with your installed version.
- apache commons compressUpdate to 1.24.0
- libcommons-compress-java Debian 12No fix published
- libcommons-compress-java Debian 13Update to 1.24.0-1
- libcommons-compress-java Debian 14Update to 1.24.0-1
- and 8 more
Check the installed version:
dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="libcommons-compress-java"'Assess your server’s risks
The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.
Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.
curl -fsSL https://patchfirst.dev/check.sh | shChannels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.
This page contains facts from public vulnerability sources. Check the original advisory before updating.
Improper Input Validation, Uncontrolled Resource Consumption vulnerability in Apache Commons Compress in TAR parsing.This issue affects Apache Commons Compress: from 1.22 before 1.24.0.
Users are recommended to upgrade to version 1.24.0, which fixes the issue.
A third party can create a malformed TAR file by manipulating file modification times headers, which when parsed with Apache Commons Compress, will cause a denial of service issue via CPU consumption.
In version 1.22 of Apache Commons Compress, support was added for file modification times with higher precision (issue # COMPRESS-612 [1]). The format for the PAX extended headers carrying this data consists of two numbers separated by a period [2], indicating seconds and subsecond precision (for example “1647221103.5998539”). The impacted fields are “atime”, “ctime”, “mtime” and “LIBARCHIVE.creationtime”. No input validation is performed prior to the parsing of header values.
Parsing of these numbers uses the BigDecimal [3] class from the JDK which has a publicly known algorithmic complexity issue when doing operations on large numbers, causing denial of service (see issue # JDK-6560193 [4]). A third party can manipulate file time headers in a TAR file by placing a number with a very long fraction (300,000 digits) or a number with exponent notation (such as “9e9999999”) within a file modification time header, and the parsing of files with these headers will take hours instead of seconds, leading to a denial of service via exhaustion of CPU resources. This issue is similar to CVE-2012-2098 [5].
[1]: https://issues.apache.org/jira/browse/COMPRESS-612 [2]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_05 [3]: https://docs.oracle.com/javase/8/docs/api/java/math/BigDecimal.html [4]: https://bugs.openjdk.org/browse/JDK-6560193 [5]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2098
Only applications using CompressorStreamFactory class (with auto-detection of file types), TarArchiveInputStream and TarFile classes to parse TAR files are impacted. Since this code was introduced in v1.22, only that version and later versions are impacted.
- Published
- Updated
Stack: system
Affected products and versions
apache commons compress
- Versions
- ≥ 1.22, < 1.24.0: Affected (maven)
Update to 1.24.0
libcommons-compress-java Debian 12
- Versions
- 1.22-1
- 1.23.0-1
- 1.24.0-1
- 1.25.0-1
- 1.27.1-1
- 1.27.1-2
All versions (7)
- 1.28.0-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Debian 13
- Affected ranges
- ECOSYSTEM: < 1.24.0-1
Update to 1.24.0-1
libcommons-compress-java Debian 14
- Affected ranges
- ECOSYSTEM: < 1.24.0-1
Update to 1.24.0-1
libcommons-compress-java Ubuntu 16.04 LTS
- Versions
- 1.9-1
- 1.10-1
- 1.10-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 18.04 LTS
- Versions
- 1.13-1
- 1.13-2
- 1.18-1~18.04
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 20.04 LTS
- Versions
- 1.18-3
- 1.19-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 22.04 LTS
- Versions
- 1.20-1
- 1.21-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 24.04 LTS
- Versions
- 1.23.0-1
- 1.24.0-1
- 1.25.0-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 25.10
- Versions
- 1.27.1-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 26.10
- Versions
- 1.27.1-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
libcommons-compress-java Ubuntu 26.04 LTS
- Versions
- 1.27.1-2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published