{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6870 is a critical memory corruption vulnerability in n/a, published on 17 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6870 and fix it if it is affected.\n\nWhat it is: CVE-2016-6870 is a critical memory corruption vulnerability in n/a, published on 17 Feb 2017. 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-2016-6870 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-6870/ (Markdown: https://insights.sbomify.com/CVE-2016-6870/index.md)","id":"CVE-2016-6870","markdown":"https://insights.sbomify.com/CVE-2016-6870/index.md","name":"CVE-2016-6870","record":{"aliases":["GHSA-392p-w329-wxhf","UBUNTU-CVE-2016-6870"],"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":"Out-of-bounds write in HHVM's multibyte string functions allows attackers to potentially execute code or cause denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","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-787","name":"Out-of-bounds Write"}],"description":"Out-of-bounds write in the (1) mb_detect_encoding, (2) mb_send_mail, and (3) mb_detect_order functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors.","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 n/a","id":"CVE-2016-6870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Integer overflow in n/a","id":"CVE-2016-6871"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2016-6866"},"products":["n/a"],"published":"2017-02-17","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-06","vendors":["n/a"]},"summary":"Out-of-bounds write in HHVM's multibyte string functions allows attackers to potentially execute code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2016-6870/"}