GHSA-cg26-4c6j-2x8h: netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges
- Source:
- OSV.dev
- Published:
- Fetched:
- Updated:
- Affects:
- io.netty.incubator:netty-incubator-codec-ohttp
https://osv.dev/vulnerability/GHSA-cg26-4c6j-2x8h ↗
netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges ## Summary: OHttpClientCodec and OHttpServerCodec retain the encrypted outer HttpContent in a handler-level cumulationBuffer. After a valid OHTTP exchange completes, the OHTTP request/response context is destroyed, but the outer cumulationBuffer is not released or reset. It remains referenced by the codec until a later inbound content frame replaces it or the handler is removed/channel is closed. This can pin attacker-influenced pooled/direct buffer capacity on idle keep-alive channels. Across many long-lived idle connections, this can create availability pressure. Affected components: * codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpClientCodec.java * codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpServerCodec.java * codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java ## Root cause: OHttpClientCodec retains inbound content into a handler-level cumulationBuffer. On LastHttpContent, it destroys only the OHttpRequestResponseContextHolder. The cumulationBuffer is released in handlerRemoved(), not immediately after successful exchange completion. OHttpServerCodec follows the same pattern: it retains inbound content into a handler-level cumulationBuffer, and on completed request/response it destroys the OHttpRequestResponseContext. The outer cumulationBuffer remains owned by the codec and is released only when the handler is removed. OHttpRequestResponseContext.parse() consumes bytes from the caller-provided outer cumulation buffer, but its destroy() path releases only the inner binary HTTP cumulation, not the codec-level outer cumulationBuffer. ## PoC: A local test only: ``` codec-ohttp/src/test/java/io/netty/incubator/codec/ohttp/OHttpCumulationBufferRetentionTest.java ``` The test reuses existing OHTTP test helpers and BouncyCastle crypto provider to perform valid completed OHTTP exchanges over EmbeddedChannel pairs. It sends both a small and a large request/response exchange, confirms completion, then reflects the private cumulationBuffer field from both OHttpClientCodec and OHttpServerCodec. Command: ``` ./mvnw -pl codec-ohttp -Dtest=OHttpCumulationBufferRetentionTest -DfailIfNoTests=false test ``` Observed output: ``` small client after completion: refCnt=1 capacity=1064 readerIndex=1064 writerIndex=1064 readableBytes=0 small server after completion: refCnt=1 capacity=1110 readerIndex=1110 writerIndex=1110 readableBytes=0 large client after completion: refCnt=1 capacity=262144 readerIndex=131114 writerIndex=131114 readableBytes=0 large server after completion: refCnt=1 capacity=262144 readerIndex=131160 writerIndex=131160 readableBytes=0 small after close: clientOldRefCnt=0 serverOldRefCnt=0 large after close: clientOldRefCnt=0 serverOldRefCnt=0 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 BUILD SUCCESS ``` Interpretation: After completion, both the client and server cumulationBuffer objects have: * refCnt=1 * readableBytes=0 * large retained capacity for t Affected: Maven:io.netty.incubator:netty-incubator-codec-ohttp Fixed in: 0.0.27.Final References: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-cg26-4c6j-2x8h https://nvd.nist.gov/vuln/detail/CVE-2026-69133 https://github.com/netty/netty-incubator-codec-ohttp/commit/a82cd85099c1a1fb78b73b068c77c8c902fc32ce https://github.com/netty/netty-incubator-codec-ohttp https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.27.Final