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

Vulnerability for com.typesafe.play:shaded-asynchttpclient:2.1.10 #12516

Open
pankajmahato-visa opened this issue Jan 31, 2025 · 0 comments
Open

Comments

@pankajmahato-visa
Copy link
Contributor

Found security vulnerability CVE-2021-37136 with severity >= 7 (severity = 7.5)
Found security vulnerability CVE-2021-37136 with severity < 9 (severity = 7.5)

Depenency tree
+--- com.typesafe.play:play-ahc-ws-standalone_2.13:2.1.10
| +--- com.typesafe.play:shaded-asynchttpclient:2.1.10

Description from CVE
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression). All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack

Explanation
The netty-codec package is vulnerable to Denial of Service (DoS). The classes and methods listed below do not properly check if the output generated upon decompressing a user-supplied file compressed with the bzip2 format is within the allowed limit. A remote attacker can exploit this behavior by submitting a specially-crafted input encoded with the bzip2 format to trigger an Out Of Memory Error (OOME), resulting in a DoS condition.

Vulnerable File(s) and Function(s):

io/netty/handler/codec/compression/Bzip2BlockDecompressor.class

decodeHuffmanData()
io/netty/handler/codec/compression/Bzip2Decoder.class

decode()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant