DHI-ysim-6523-ndmu-e3lo

Source
https://scout.docker.com/v/DHI-ysim-6523-ndmu-e3lo
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-ysim-6523-ndmu-e3lo.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-ysim-6523-ndmu-e3lo
Upstream
Published
2026-11-14T01:54:29Z
Modified
2026-11-17T10:00:14Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
snappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur…
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.

Version 1.1.10.1 contains a patch for this issue.

References

Affected packages

Docker Hardened Images:Debian:13 / druid-36-fips

Package

Name
druid-36-fips
Purl
pkg:deb/dhi/druid-36-fips

Affected ranges

Affected versions

36.*
36.0.0-1
36.0.0-4
36.0.0-5
36.0.0-6
36.0.0-7
36.0.0-8
36.0.0-9
36.0.0-10
36.0.0-11
36.0.0-12
36.0.0-13
36.0.0-14
36.0.0-15
36.0.0-16
36.0.0-17
36.0.0-18
36.0.0-19
36.0.0-20
36.0.0-21
36.0.0-22
36.0.0-23
36.0.0-24
36.0.0-25
36.0.0-26
36.0.0-27
36.0.0-28
36.0.0-29
36.0.0-30
36.0.0-31
36.0.0-32
36.0.0-33

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-ysim-6523-ndmu-e3lo.json"

Docker Hardened Images:Debian:13 / druid-36

Package

Name
druid-36
Purl
pkg:deb/dhi/druid-36

Affected ranges

Affected versions

36.*
36.0.0-0
36.0.0-1
36.0.0-4
36.0.0-5
36.0.0-6
36.0.0-7
36.0.0-8
36.0.0-9
36.0.0-10
36.0.0-11
36.0.0-12
36.0.0-13
36.0.0-14
36.0.0-15
36.0.0-16
36.0.0-17
36.0.0-18
36.0.0-19
36.0.0-20
36.0.0-21
36.0.0-22
36.0.0-23
36.0.0-24
36.0.0-25
36.0.0-26
36.0.0-27
36.0.0-28
36.0.0-29
36.0.0-30
36.0.0-31
36.0.0-32
36.0.0-33

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-ysim-6523-ndmu-e3lo.json"