{"answers":{"affected":"2 open source packages ship an affected version, including github.com/envoyproxy/envoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9901 in the wild and no public exploit code.","fix":"Upgrade github.com/envoyproxy/envoy to 1.9.1 or later.","what":"CVE-2019-9901 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-9901 and fix it if it is affected.\n\nWhat it is: CVE-2019-9901 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-9901 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/envoyproxy/envoy (Go): affected all versions; fixed in 1.9.1\n- github.com/envoyproxy/envoy (Go): affected all versions; fixed in 1.9.1\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-9901/ (Markdown: https://insights.sbomify.com/CVE-2019-9901/index.md)","id":"CVE-2019-9901","markdown":"https://insights.sbomify.com/CVE-2019-9901/index.md","name":"CVE-2019-9901","record":{"aliases":["GHSA-2wmf-p7f8-w42h","GHSA-xcx5-93pw-jw2w"],"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":"Remote attackers can bypass access control policies by sending non-normalized HTTP paths, potentially accessing restricted backend resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"envoy","vendor":"envoyproxy"}],"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-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"Envoy 1.9.0 and before does not normalize HTTP URL paths. A remote attacker may craft a relative path, e.g., something/../admin, to bypass access control, e.g., a block on /admin. A backend server could then interpret the non-normalized path and provide an attacker access beyond the scope provided for by the access control policy.","ecosystems":["Go"],"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":"EnvoyProxy Envoy Missing HTTP URL path normalization","id":"CVE-2019-9901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"security_feature_bypass","year":"2019"},"n_packages":2,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-9903"},"packages":[{"ecosystem":"Go","fixed":["1.9.1"],"introduced":["0"],"last_affected":[],"package":"github.com/envoyproxy/envoy","purl":null,"source":"GHSA-2wmf-p7f8-w42h"},{"ecosystem":"Go","fixed":["1.9.1"],"introduced":["0"],"last_affected":[],"package":"github.com/envoyproxy/envoy","purl":"pkg:golang/github.com/envoyproxy/envoy","source":"GHSA-2wmf-p7f8-w42h"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2019-9900"},"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Remote attackers can bypass access control policies by sending non-normalized HTTP paths, potentially accessing restricted backend resources.","url":"https://insights.sbomify.com/CVE-2019-9901/"}