Improper Validation of Specified Index, Position, or Offset in Input Affecting log4j package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.18% (56th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS9-LOG4J-5831113
  • published9 Aug 2023
  • disclosed16 Jun 2023

Introduced: 16 Jun 2023

CVE-2023-34455  (opens in a new tab)
CWE-1285  (opens in a new tab)

How to fix?

There is no fixed version for Centos:9 log4j.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j package and not the log4j package as distributed by Centos. See How to fix? for Centos:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1