Skip to content

[馃惛 Frogbot] Update version of io.netty:netty-codec-http to 4.1.135.Final - #134

Open
github-actions[bot] wants to merge 1 commit into
masterfrom
frogbot-io.netty_netty-codec-http-69f415309fc0c7754fd7525fe16b9620
Open

[馃惛 Frogbot] Update version of io.netty:netty-codec-http to 4.1.135.Final#134
github-actions[bot] wants to merge 1 commit into
masterfrom
frogbot-io.netty_netty-codec-http-69f415309fc0c7754fd7525fe16b9620

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

馃毃 This automated pull request was created by Frogbot and fixes the below:

馃摝 Vulnerable Dependencies

Severity ID Contextual Analysis Direct Dependencies Impacted Dependency Fixed Versions
critical (not applicable)
Critical
CVE-2026-42584 Not Applicable org.mock-server:mockserver-netty:5.14.0 io.netty:netty-codec-http 4.1.130.Final [4.1.133.Final]
[4.2.13.Final]

馃敄 Details

Vulnerability Details

Contextual Analysis: Not Applicable
Direct Dependencies: org.mock-server:mockserver-netty:5.14.0
Impacted Dependency: io.netty:netty-codec-http:4.1.130.Final
Fixed Versions: [4.1.133.Final], [4.2.13.Final]
CVSS V3: 9.1

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message鈥檚 body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.


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

Successfully merging this pull request may close these issues.

1 participant