{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-7246 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-7246 is a medium-severity vulnerability in Google gRPC, published on 6 Aug 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-7246 and fix it if it is affected.\n\nWhat it is: CVE-2024-7246 is a medium-severity vulnerability in Google gRPC, published on 6 Aug 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-7246 in the wild and no public exploit code.\n\nAffected product: Google gRPC. 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-7246/ (Markdown: https://insights.sbomify.com/CVE-2024-7246/index.md)","id":"CVE-2024-7246","markdown":"https://insights.sbomify.com/CVE-2024-7246/index.md","name":"CVE-2024-7246","record":{"aliases":["AZL-47442","AZL-47571","BELL-CVE-2024-7246","DEBIAN-CVE-2024-7246","ECHO-776e-6420-85f8","GHSA-ghwg-gpp4-w4x3","OESA-2024-2064","UBUNTU-CVE-2024-7246"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"gRPC library","requires_auth":"none","summary":"Attackers can poison HPACK tables to leak HTTP header keys and cause request failures in gRPC clients communicating via HTTP/2 proxies.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"grpc","vendor":"grpc"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-440","name":"Expected Behavior Violation"}],"description":"It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values.\n\nThis occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table.\n\nPlease update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HPACK table poisoning in gRPC C++, Python \u0026 Ruby","id":"CVE-2024-7246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Element Pack – Widgets, Templates \u0026 Addons for Elementor","id":"CVE-2024-7247"},"packages":[],"prev":{"headline":"Panda Security Dome VPN Incorrect Permission Assignment Local Privilege Escalation Vulnerability","id":"CVE-2024-7245"},"products":["gRPC"],"published":"2024-08-06","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9431","kev_date_added":null,"published":"2017-06-05"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2017-8359","kev_date_added":null,"published":"2017-04-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7860","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7861","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.1,"headline":"gRPC-Go has an authorization bypass via missing leading slash in :path","id":"CVE-2026-33186","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Denial of Service in gRPC Core","id":"CVE-2023-4785","kev_date_added":null,"published":"2023-09-13"},{"cvss_score":7.5,"headline":"Denial-of-Service in gRPC","id":"CVE-2023-33953","kev_date_added":null,"published":"2023-08-09"}],"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":"2024-08-06","vendors":["Google"]},"summary":"Attackers can poison HPACK tables to leak HTTP header keys and cause request failures in gRPC clients communicating via HTTP/2 proxies.","url":"https://insights.sbomify.com/CVE-2024-7246/"}