Absent Input Validation in BinaryHttpParser

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2024-40642: 0.68% estimated exploitation activity in the next 30 days; percentile 52.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary BinaryHttpParser does not properly validate input values thus giving attackers almost complete control over the HTTP requests constructed from the parsed output. Attackers can abuse several issues individually to perform various injection attacks including HTTP request smuggling, desync attacks, HTTP header injections, request queue poisoning, caching attacks and Server Side Request Forgery (SSRF). Attacker could also combine several issues to create well-formed messages for other text-based protocols which may result in attacks beyond the HTTP protocol. Details Path, Authority, Scheme The BinaryHttpParser class implements the readRequestHead method which performs most of the relevant parsing of the received request. The data structure prefixes values with a variable length integer value. The algorithm to create a variable length integer value is below: The parsing code below first gets the lengths of the values from the prefixed variable length integer. After it has all of…

Published by the source

18 Jul 2024, 22:14 UTC

Last modified by the source

19 Jul 2024, 14:17 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q8f2-hxq5-cp4h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-40642

Advisory: Absent Input Validation in BinaryHttpParser
IDs: CVE-2024-40642, GHSA-q8f2-hxq5-cp4h
Record: https://patchnext.com/advisories/cve-2024-40642 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.netty.incubator:netty-incubator-codec-bhttp 0.0.13.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty.incubator:netty-incubator-codec-bhttp: affected < 0.0.13.Final; fixed in 0.0.13.Final

## Suggested inspection (read-only)
- Maven io.netty.incubator:netty-incubator-codec-bhttp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty.incubator:netty-incubator-codec-bhttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q8f2-hxq5-cp4h (GitHub-reviewed advisory GHSA-q8f2-hxq5-cp4h lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-bhttp >=0 <0.0.13.Final)

Commands are suggestions: review each one before running it.