Bug 1221412 (CVE-2023-42503) - VUL-0: CVE-2023-42503: apache-commons-compress: Algorithmic complexity vulnerability in the sorting algorithms in bzip2 compressing stream (BZip2CompressorOutputStream) in Apache Commons Compress before 1.4.1 allows remote attackers to cause a denial ...
Summary: VUL-0: CVE-2023-42503: apache-commons-compress: Algorithmic complexity vulner...
Status: RESOLVED FIXED
Alias: CVE-2023-42503
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/378185/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-14 14:28 UTC by SMASH SMASH
Modified: 2024-06-10 12:35 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-14 14:28:25 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42503
https://seclists.org/oss-sec/2023/q3/177
http://www.openwall.com/lists/oss-security/2023/09/13/3
https://bugs.openjdk.org/browse/JDK-6560193
https://www.cve.org/CVERecord?id=CVE-2012-2098
https://www.cve.org/CVERecord?id=CVE-2023-42503
https://lists.apache.org/thread/5xwcyr600mn074vgxq92tjssrchmc93c
https://security.netapp.com/advisory/ntap-20231020-0003/
Comment 1 Fridrich Strba 2024-03-18 13:11:50 UTC
This is pretty old stuff. Do we really have something vulnerable? The version in sle15sp2 is patched since ages.
Comment 2 Gabriele Sonnu 2024-06-10 12:35:28 UTC
All done, closing.