{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11925 is a critical memory corruption vulnerability in Facebook HHVM, published on 6 Sep 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-11925 and fix it if it is affected.\n\nWhat it is: CVE-2019-11925 is a critical memory corruption vulnerability in Facebook HHVM, published on 6 Sep 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-11925 in the wild and no public exploit code.\n\nAffected product: Facebook HHVM. 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-11925/ (Markdown: https://insights.sbomify.com/CVE-2019-11925/index.md)","id":"CVE-2019-11925","markdown":"https://insights.sbomify.com/CVE-2019-11925/index.md","name":"CVE-2019-11925","record":{"aliases":["GHSA-xm5g-27h5-6568","UBUNTU-CVE-2019-11925"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HHVM runtime","requires_auth":"none","summary":"Attacker can trigger out-of-bounds memory access via malicious JPEG input in HHVM, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"hhvm","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-125","name":"Out-of-bounds Read"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Insufficient boundary checks when processing the JPEG APP12 block marker in the GD extension could allow access to out-of-bounds memory via a maliciously constructed invalid JPEG input. This issue affects HHVM versions prior to 3.30.9, all versions between 4.0.0 and 4.8.3, all versions between 4.9.0 and 4.15.2, and versions 4.16.0 to 4.16.3, 4.17.0 to 4.17.2, 4.18.0 to 4.18.1, 4.19.0, 4.20.0 to 4.20.1.","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 HHVM","id":"CVE-2019-11925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in HHVM","id":"CVE-2019-11926"},"packages":[],"prev":{"headline":"Denial of service in fizz","id":"CVE-2019-11924"},"products":["HHVM"],"published":"2019-09-06","related":[{"cvss_score":9.8,"headline":"HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension.","id":"CVE-2022-36937","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":9.8,"headline":"Use after free in HHVM","id":"CVE-2020-1900","kev_date_added":null,"published":"2021-03-11"},{"cvss_score":9.8,"headline":"Integer overflow in HHVM","id":"CVE-2020-1916","kev_date_added":null,"published":"2021-03-10"},{"cvss_score":9.8,"headline":"Memory corruption in HHVM","id":"CVE-2020-1917","kev_date_added":null,"published":"2021-03-10"},{"cvss_score":9.8,"headline":"Integer overflow in HHVM","id":"CVE-2021-24025","kev_date_added":null,"published":"2021-03-10"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2016-1000004","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2016-1000005","kev_date_added":null,"published":"2020-02-19"}],"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":"Attacker can trigger out-of-bounds memory access via malicious JPEG input in HHVM, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2019-11925/"}