{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23452 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-23452 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-23452 is a high-severity vulnerability in Apache bRPC, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-23452 and fix it if it is affected.\n\nWhat it is: CVE-2024-23452 is a high-severity vulnerability in Apache bRPC, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-23452 in the wild and no public exploit code.\n\nAffected product: Apache bRPC. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-23452/ (Markdown: https://insights.sbomify.com/CVE-2024-23452/index.md)","id":"CVE-2024-23452","markdown":"https://insights.sbomify.com/CVE-2024-23452/index.md","name":"CVE-2024-23452","record":{"aliases":["GHSA-2862-59r4-c989"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"bRPC HTTP server","requires_auth":"none","summary":"Attackers can smuggle HTTP requests in Apache bRPC due to non-compliant parsing, potentially bypassing security controls or corrupting data.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"brpc","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request.\n\nVulnerability Cause Description：\n\nThe http_parser does not comply with the RFC-7230 HTTP 1.1 specification.\n\nAttack scenario:\nIf 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.\nOne 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. \n\nSolution:\nYou can choose one solution from below:\n1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link:  https://github.com/apache/brpc/releases/tag/1.8.0\n 2. Apply this patch:  https://github.com/apache/brpc/pull/2518","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache bRPC: HTTP request smuggling vulnerability","id":"CVE-2024-23452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded credentials in Android Spoon application","id":"CVE-2024-23453"},"packages":[],"prev":{"headline":"Elasticsearch Incorrect Authorization in the Remote Cluster Security API key based security model","id":"CVE-2024-23451"},"products":["Apache bRPC"],"published":"2024-02-08","related":[{"cvss_score":9.8,"headline":"Apache bRPC: Remote command injection vulnerability in heap builtin service","id":"CVE-2025-60021","kev_date_added":null,"published":"2026-01-16"},{"cvss_score":9.8,"headline":"Apache bRPC: ServerOptions.pid_file may cause arbitrary code execution","id":"CVE-2023-31039","kev_date_added":null,"published":"2023-05-08"},{"cvss_score":7.5,"headline":"Apache bRPC: Stack Exhaustion via Unbounded Recursion in JSON Parser","id":"CVE-2025-59789","kev_date_added":null,"published":"2025-12-01"},{"cvss_score":7.5,"headline":"Apache bRPC: Redis Parser Remote Denial of Service","id":"CVE-2025-54472","kev_date_added":null,"published":"2025-08-14"},{"cvss_score":6.1,"headline":"Apache bRPC: The builtin service rpcz page has an XSS attack vulnerability","id":"CVE-2023-45757","kev_date_added":null,"published":"2023-10-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-04","vendors":["Apache Software Foundation"]},"summary":"Attackers can smuggle HTTP requests in Apache bRPC due to non-compliant parsing, potentially bypassing security controls or corrupting data.","url":"https://insights.sbomify.com/CVE-2024-23452/"}