{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11921 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11921 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11921 is a critical memory corruption vulnerability in Facebook Proxygen, published on 25 Jul 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-11921 and fix it if it is affected.\n\nWhat it is: CVE-2019-11921 is a critical memory corruption vulnerability in Facebook Proxygen, published on 25 Jul 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-11921 in the wild and no public exploit code.\n\nAffected product: Facebook Proxygen. 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-11921/ (Markdown: https://insights.sbomify.com/CVE-2019-11921/index.md)","id":"CVE-2019-11921","markdown":"https://insights.sbomify.com/CVE-2019-11921/index.md","name":"CVE-2019-11921","record":{"aliases":["GHSA-87xc-5jfw-gv68"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Proxygen HTTP library","requires_auth":"none","summary":"An out-of-bounds write in Proxygen allows attackers to execute code or cause denial of service via crafted packets in specific configurations.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"proxygen","vendor":"facebook"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An out of bounds write is possible via a specially crafted packet in certain configurations of Proxygen due to improper handling of Base64 when parsing malformed binary content in Structured HTTP Headers. This issue affects versions of proxygen prior to v2019.07.22.00.","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":"Memory corruption in Proxygen","id":"CVE-2019-11921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Race condition in Zstandard","id":"CVE-2019-11922"},"packages":[],"prev":{"headline":"Missing authorization in Access Professional Edition","id":"CVE-2019-11899"},"products":["Proxygen"],"published":"2019-07-25","related":[{"cvss_score":9.8,"headline":"Use after free in proxygen","id":"CVE-2020-1897","kev_date_added":null,"published":"2020-05-18"},{"cvss_score":9.8,"headline":"Use after free in Proxygen","id":"CVE-2019-11940","kev_date_added":null,"published":"2019-12-04"},{"cvss_score":7.5,"headline":"Proxygen fails to validate that a secondary auth manager is set before dereferencing it.","id":"CVE-2018-6343","kev_date_added":null,"published":"2018-12-31"},{"cvss_score":5.3,"headline":"Denial of service in proxygen","id":"CVE-2025-55181","kev_date_added":null,"published":"2025-12-02"}],"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":["Facebook"]},"summary":"An out-of-bounds write in Proxygen allows attackers to execute code or cause denial of service via crafted packets in specific configurations.","url":"https://insights.sbomify.com/CVE-2019-11921/"}