CVE intelligence and bounded remediation

CVE-2024-23452 — Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request

High CVSS 7.5

Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request. Vulnerability Cause Description： The http_parser does not comply with the RFC-7230 HTTP 1.1 specification. Attack scenario: If a message is received with both a Transfer-Encoding and a Content-Length header field, such a message might indicate an attempt to perform request smuggling or response splitting. One particular attack scenario is that a bRPC made http server on the backend receiving requests in one persistent connection from frontend server that uses TE to parse request with the logic that 'chunk' is contained in the TE field. in that case an attacker can smuggle a request into the connection to the backend server. Solution: You can choose one solution from below: 1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link: https://github.com/apache/brpc/releases/tag/1.8.0 2. Apply this patch: https://github.com/apache/brpc/pull/2518

Severity
High
CVSS
7.5 (3.1)
Published
2024-02-08
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-444

Affected products

  • apache / brpc

Matched remediation archetype

HTTP request smuggling and message-boundary ambiguity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory every proxy, CDN, gateway, load balancer, service mesh, and application server hop on affected request paths.
  • Compare documented parsing and normalization behavior for message length, transfer coding, duplicate headers, and protocol translation.
  • Identify connection reuse and which downstream services trust headers added by intermediaries.

Remediate safely

  • Update affected intermediaries and origin servers and align them on a single standards-compliant request framing policy.
  • Reject ambiguous length, transfer-coding, duplicate, malformed, and unsupported framing before forwarding.
  • Normalize or remove hop-by-hop and identity headers at one controlled boundary and add multi-hop regression tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.