{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-9900 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-9900 is a medium-severity vulnerability in Envoyproxy Envoy, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9900 and fix it if it is affected.\n\nWhat it is: CVE-2019-9900 is a medium-severity vulnerability in Envoyproxy Envoy, published on 25 Apr 2019. 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-2019-9900 in the wild and no public exploit code.\n\nAffected product: Envoyproxy Envoy. 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-2019-9900/ (Markdown: https://insights.sbomify.com/CVE-2019-9900/index.md)","id":"CVE-2019-9900","markdown":"https://insights.sbomify.com/CVE-2019-9900/index.md","name":"CVE-2019-9900","record":{"aliases":["GHSA-h9r7-c397-3wqr","GHSA-x74r-f4mw-c32h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Envoy proxy","requires_auth":"none","summary":"Attackers can bypass header matching rules in Envoy proxy by embedding NUL characters in HTTP headers, gaining unauthorized access to resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"envoy","vendor":"envoyproxy"},{"product":"openshift_service_mesh","vendor":"redhat"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:H/AV:N/A:L/C:L/I:L/PR:N/S:C/UI:N","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"When parsing HTTP/1.x header values, Envoy 1.9.0 and before does not reject embedded zero characters (NUL, ASCII 0x0). This allows remote attackers crafting header values containing embedded NUL characters to potentially bypass header matching rules, gaining access to unauthorized resources.","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":"Security feature bypass in n/a","id":"CVE-2019-9900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"EnvoyProxy Envoy Missing HTTP URL path normalization","id":"CVE-2019-9901"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2019-9898"},"products":["n/a"],"published":"2019-04-25","related":[{"cvss_score":10,"headline":"Trivial authentication bypass in Envoy","id":"CVE-2022-29226","kev_date_added":null,"published":"2022-06-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-18801","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-18802","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2020-35470","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.6,"headline":"Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata","id":"CVE-2024-23324","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":8.6,"headline":"Envoy vulnerable to OAuth2 credentials exploit with permanent validity","id":"CVE-2023-35941","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":8.6,"headline":"Incorrect handling of H2 GOAWAY + SETTINGS frames","id":"CVE-2021-39162","kev_date_added":null,"published":"2021-09-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass header matching rules in Envoy proxy by embedding NUL characters in HTTP headers, gaining unauthorized access to resources.","url":"https://insights.sbomify.com/CVE-2019-9900/"}