CVE-2024-40642

8.1 HIGH

📋 TL;DR

This vulnerability in netty incubator codec.bhttp allows attackers to manipulate binary HTTP parsing to perform injection attacks. Attackers can achieve HTTP request smuggling, header injection, SSRF, and other protocol-based attacks by exploiting improper input validation. Systems using vulnerable versions of netty-incubator-codec-ohttp for binary HTTP parsing are affected.

💻 Affected Systems

Products:
  • netty-incubator-codec-ohttp
Versions: All versions before 0.0.13.Final
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects applications using BinaryHttpParser class for binary HTTP parsing. Standard HTTP parsing in netty is not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete control over HTTP requests leading to server compromise, data exfiltration, and lateral movement within the network via SSRF and request smuggling.

🟠

Likely Case

HTTP request smuggling enabling cache poisoning, session hijacking, and credential theft through crafted requests.

🟢

If Mitigated

Limited impact with proper network segmentation and input validation at application layer, though binary HTTP parsing remains vulnerable.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires sending specially crafted binary HTTP requests to vulnerable endpoints. No public exploit code available at disclosure time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.0.13.Final

Vendor Advisory: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-q8f2-hxq5-cp4h

Restart Required: Yes

Instructions:

1. Update netty-incubator-codec-ohttp dependency to version 0.0.13.Final. 2. Rebuild and redeploy affected applications. 3. Restart services using the updated library.

🔧 Temporary Workarounds

No workarounds available

all

The vendor advisory states there are no known workarounds for this vulnerability.

🧯 If You Can't Patch

  • Implement strict input validation at application layer for all HTTP request parameters
  • Deploy WAF with rules to detect and block malformed binary HTTP requests

🔍 How to Verify

Check if Vulnerable:

Check pom.xml or build.gradle for netty-incubator-codec-ohttp dependency version below 0.0.13.Final

Check Version:

mvn dependency:tree | grep netty-incubator-codec-ohttp OR gradle dependencies | grep netty-incubator-codec-ohttp

Verify Fix Applied:

Verify netty-incubator-codec-ohttp version is 0.0.13.Final or higher in dependency files

📡 Detection & Monitoring

Log Indicators:

  • Unusual binary HTTP request patterns
  • HTTP parsing errors in application logs
  • Unexpected HTTP header values

Network Indicators:

  • Malformed binary HTTP requests
  • Unusual request sizes or patterns in binary HTTP traffic

SIEM Query:

source="application_logs" AND ("BinaryHttpParser" OR "binary http" OR "netty-incubator") AND (error OR exception OR malformed)

🔗 References

📤 Share & Export