{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1892 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1892 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1892 is a high-severity vulnerability in Facebook HHVM, published on 3 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-1892 and fix it if it is affected.\n\nWhat it is: CVE-2020-1892 is a high-severity vulnerability in Facebook HHVM, published on 3 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-1892 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-2020-1892/ (Markdown: https://insights.sbomify.com/CVE-2020-1892/index.md)","id":"CVE-2020-1892","markdown":"https://insights.sbomify.com/CVE-2020-1892/index.md","name":"CVE-2020-1892","record":{"aliases":["GHSA-r2qf-75cq-8rxc","UBUNTU-CVE-2020-1892"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HHVM runtime","requires_auth":"none","summary":"Insufficient boundary checks in HHVM's JSON parser allow attackers to read out-of-bounds memory, causing information leaks or denial of service.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"hhvm","vendor":"facebook"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Insufficient boundary checks when decoding JSON in JSON_parser allows read access to out of bounds memory, potentially leading to information leak and DOS. This issue affects HHVM 4.45.0, 4.44.0, 4.43.0, 4.42.0, 4.41.0, 4.40.0, 4.39.0, versions between 4.33.0 and 4.38.0 (inclusive), versions between 4.9.0 and 4.32.0 (inclusive), and versions prior to 4.8.7.","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":"Information disclosure in HHVM","id":"CVE-2020-1892","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in HHVM","id":"CVE-2020-1893"},"packages":[],"prev":{"headline":"Memory corruption in WhatsApp Android","id":"CVE-2020-1891"},"products":["HHVM"],"published":"2020-03-03","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":"Insufficient boundary checks in HHVM's JSON parser allow attackers to read out-of-bounds memory, causing information leaks or denial of service.","url":"https://insights.sbomify.com/CVE-2020-1892/"}