| Title | xerial の snappy-java における制限またはスロットリング無しのリソースの割り当てに関する脆弱性 |
|---|---|
| Summary | xerial の snappy-java には、制限またはスロットリング無しのリソースの割り当てに関する脆弱性が存在します。 |
| Possible impacts | サービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダアドバイザリまたはパッチ情報が公開されています。参考情報を参照して適切な対策を実施してください。 |
| Publication Date | June 15, 2023, midnight |
| Registration Date | Dec. 8, 2023, 6:21 p.m. |
| Last Update | Dec. 8, 2023, 6:21 p.m. |
| CVSS3.0 : 重要 | |
| Score | 7.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| xerial |
| snappy-java 1.1.10.1 未満 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2023年12月08日] 掲載 |
Dec. 8, 2023, 6:21 p.m. |
| Summary | 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. |
|---|---|
| Publication Date | June 16, 2023, 3:15 a.m. |
| Registration Date | June 16, 2023, 10 a.m. |
| Last Update | Nov. 21, 2024, 5:07 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:xerial:snappy-java:*:*:*:*:*:*:*:* | 1.1.10.1 | ||||