First published: Tue Jun 04 2024(Updated: )
netty-incubator-codec-ohttp is the OHTTP implementation for netty. BoringSSLAEADContext keeps track of how many OHTTP responses have been sent and uses this sequence number to calculate the appropriate nonce to use with the encryption algorithm. Unfortunately, two separate errors combine which would allow an attacker to cause the sequence number to overflow and thus the nonce to repeat.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.netty.incubator:netty-incubator-codec-ohttp | >=0.0.3.Final<0.0.11.Final | 0.0.11.Final |
Netty Netty-incubator-codec-ohttp | >=0.0.3<0.0.11 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-36121 has been rated as high severity due to its potential impact on the confidentiality and integrity of data transmitted using OHTTP.
To mitigate CVE-2024-36121, update the netty-incubator-codec-ohttp package to version 0.0.11.Final or later.
CVE-2024-36121 affects netty-incubator-codec-ohttp versions from 0.0.3.Final up to, but not including, 0.0.11.Final.
CVE-2024-36121 can allow attackers to exploit vulnerabilities in OHTTP responses, potentially compromising data during transmission.
Yes, CVE-2024-36121 is specifically related to the BoringSSLAEADContext within the netty-incubator-codec-ohttp component.