Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2023-34455 (High) detected in snappy-java-1.1.8.4.jar - autoclosed #2885

Closed
1 task
mend-for-github.aaakk.us.kg bot opened this issue Jun 20, 2023 · 1 comment
Closed
1 task
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource untriaged Require the attention of the repository maintainers and may need to be prioritized

Comments

@mend-for-github.aaakk.us.kg
Copy link
Contributor

CVE-2023-34455 - High Severity Vulnerability

Vulnerable Library - snappy-java-1.1.8.4.jar

snappy-java: A fast compression/decompression library

Library home page: https://github.com/xerial/snappy-java

Path to dependency file: /build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.xerial.snappy/snappy-java/1.1.8.4/66f0d56454509f6e36175f2331572e250e04a6cc/snappy-java-1.1.8.4.jar

Dependency Hierarchy:

  • snappy-java-1.1.8.4.jar (Vulnerable Library)

Found in HEAD commit: b4413a769a13ddee13ac168bdb4ef94b4248a169

Found in base branch: main

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.

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:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

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


  • Check this box to open an automated fix PR
@mend-for-github.aaakk.us.kg mend-for-github.aaakk.us.kg bot added the Mend: dependency security vulnerability Security vulnerability detected by WhiteSource label Jun 20, 2023
@github-actions github-actions bot added the untriaged Require the attention of the repository maintainers and may need to be prioritized label Jun 20, 2023
@mend-for-github.aaakk.us.kg mend-for-github.aaakk.us.kg bot changed the title CVE-2023-34455 (High) detected in snappy-java-1.1.8.4.jar CVE-2023-34455 (High) detected in snappy-java-1.1.8.4.jar - autoclosed Jun 21, 2023
@mend-for-github.aaakk.us.kg
Copy link
Contributor Author

✔️ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource untriaged Require the attention of the repository maintainers and may need to be prioritized
Projects
None yet
Development

No branches or pull requests

0 participants