You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /server/plugins/kafka-event-sink/pom.xml
Path to vulnerable library: /server/plugins/kafka-event-sink/pom.xml
Dependency Hierarchy:
kafka-clients-2.4.0.jar (Root Library)
❌ snappy-java-1.1.7.3.jar (Vulnerable Library)
Found in base branch: master
Vulnerability Details
snappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing an unrecoverable fatal error.
The function compress(char[] input) in the file Snappy.java receives an array of characters and compresses it. It does so by multiplying the length by 2 and passing it to the rawCompress` function.
Since the length is not tested, the multiplication by two can cause an integer overflow and become negative. The rawCompress function then uses the received length and passes it to the natively compiled maxCompressedLength function, using the returned value to allocate a byte array.
Since the maxCompressedLength function treats the length as an unsigned integer, it doesn’t care that it is negative, and it returns a valid value, which is casted to a signed integer by the Java engine. If the result is negative, a java.lang.NegativeArraySizeException exception will be raised while trying to allocate the array buf. On the other side, if the result is positive, the buf array will successfully be allocated, but its size might be too small to use for the compression, causing a fatal Access Violation error.
The same issue exists also when using the compress functions that receive double, float, int, long and short, each using a different multiplier that may cause the same issue. The issue most likely won’t occur when using a byte array, since creating a byte array of size 0x80000000 (or any other negative value) is impossible in the first place.
mend-for-github-combot
changed the title
CVE-2023-34454 (Medium) detected in snappy-java-1.1.7.3.jar
CVE-2023-34454 (High) detected in snappy-java-1.1.7.3.jar
Jul 31, 2023
mend-for-github-combot
changed the title
CVE-2023-34454 (High) detected in snappy-java-1.1.7.3.jar
CVE-2023-34454 (High) detected in snappy-java-1.1.7.3.jar - autoclosed
Apr 13, 2024
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
mend-for-github-combot
changed the title
CVE-2023-34454 (High) detected in snappy-java-1.1.7.3.jar - autoclosed
CVE-2023-34454 (High) detected in snappy-java-1.1.7.3.jar
Jun 16, 2024
CVE-2023-34454 - High Severity Vulnerability
snappy-java: A fast compression/decompression library
Library home page: https://github.com/xerial/snappy-java
Path to dependency file: /server/plugins/kafka-event-sink/pom.xml
Path to vulnerable library: /server/plugins/kafka-event-sink/pom.xml
Dependency Hierarchy:
Found in base branch: master
snappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing an unrecoverable fatal error.
The function
compress(char[] input)
in the fileSnappy.java
receives an array of characters and compresses it. It does so by multiplying the length by 2 and passing it to the rawCompress` function.Since the length is not tested, the multiplication by two can cause an integer overflow and become negative. The rawCompress function then uses the received length and passes it to the natively compiled maxCompressedLength function, using the returned value to allocate a byte array.
Since the maxCompressedLength function treats the length as an unsigned integer, it doesn’t care that it is negative, and it returns a valid value, which is casted to a signed integer by the Java engine. If the result is negative, a
java.lang.NegativeArraySizeException
exception will be raised while trying to allocate the arraybuf
. On the other side, if the result is positive, thebuf
array will successfully be allocated, but its size might be too small to use for the compression, causing a fatal Access Violation error.The same issue exists also when using the
compress
functions that receive double, float, int, long and short, each using a different multiplier that may cause the same issue. The issue most likely won’t occur when using a byte array, since creating a byte array of size 0x80000000 (or any other negative value) is impossible in the first place.Version 1.1.10.1 contains a patch for this issue.
Publish Date: 2023-06-15
URL: CVE-2023-34454
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-fjpj-2g6w-x25r
Release Date: 2023-06-15
Fix Resolution (org.xerial.snappy:snappy-java): 1.1.10.1
Direct dependency fix Resolution (org.apache.kafka:kafka-clients): 2.4.1
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: