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: /spring-distributed-tracing/audit-flume/pom.xml
Path to vulnerable library: /root/.m2/repository/org/xerial/snappy/snappy-java/1.1.4/snappy-java-1.1.4.jar,/root/.m2/repository/org/xerial/snappy/snappy-java/1.1.4/snappy-java-1.1.4.jar
Dependency Hierarchy:
flume-ng-embedded-agent-1.9.0.jar (Root Library)
flume-file-channel-1.9.0.jar
❌ snappy-java-1.1.4.jar (Vulnerable Library)
Found in base branch: master
Vulnerability Details
snappy-java is a fast compressor/decompressor for Java. Due to use of an unchecked chunk length, an unrecoverable fatal error can occur in versions prior to 1.1.10.1.
The code in the function hasNextChunk in the fileSnappyInputStream.java checks if a given stream has more chunks to read. It does that by attempting to read 4 bytes. If it wasn’t possible to read the 4 bytes, the function returns false. Otherwise, if 4 bytes were available, the code treats them as the length of the next chunk.
In the case that the compressed variable is null, a byte array is allocated with the size given by the input data. Since the code doesn’t test the legality of the chunkSize variable, it is possible to pass a negative number (such as 0xFFFFFFFF which is -1), which will cause the code to raise a java.lang.NegativeArraySizeException exception. A worse case would happen when passing a huge positive value (such as 0x7FFFFFFF), which would raise the fatal java.lang.OutOfMemoryError error.
CVE-2023-34455 - High Severity Vulnerability
Vulnerable Library - snappy-java-1.1.4.jar
snappy-java: A fast compression/decompression library
Library home page: https://github.com/xerial/snappy-java
Path to dependency file: /spring-distributed-tracing/audit-flume/pom.xml
Path to vulnerable library: /root/.m2/repository/org/xerial/snappy/snappy-java/1.1.4/snappy-java-1.1.4.jar,/root/.m2/repository/org/xerial/snappy/snappy-java/1.1.4/snappy-java-1.1.4.jar
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
snappy-java is a fast compressor/decompressor for Java. Due to use of an unchecked chunk length, an unrecoverable fatal error can occur in versions prior to 1.1.10.1.
The code in the function hasNextChunk in the fileSnappyInputStream.java checks if a given stream has more chunks to read. It does that by attempting to read 4 bytes. If it wasn’t possible to read the 4 bytes, the function returns false. Otherwise, if 4 bytes were available, the code treats them as the length of the next chunk.
In the case that the
compressed
variable is null, a byte array is allocated with the size given by the input data. Since the code doesn’t test the legality of thechunkSize
variable, it is possible to pass a negative number (such as 0xFFFFFFFF which is -1), which will cause the code to raise ajava.lang.NegativeArraySizeException
exception. A worse case would happen when passing a huge positive value (such as 0x7FFFFFFF), which would raise the fataljava.lang.OutOfMemoryError
error.Version 1.1.10.1 contains a patch for this issue.
Publish Date: 2023-06-15
URL: CVE-2023-34455
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-qcwq-55hx-v3vh
Release Date: 2023-06-15
Fix Resolution: org.xerial.snappy:snappy-java:1.1.10.1
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: