{"answers":{"affected":"2 open source packages ship an affected version, including hermes-engine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1914 in the wild and no public exploit code.","fix":"Upgrade hermes-engine to 0.7.2 or later.","what":"CVE-2020-1914 is a critical memory corruption vulnerability in Facebook Hermes, published on 8 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1914 and fix it if it is affected.\n\nWhat it is: CVE-2020-1914 is a critical memory corruption vulnerability in Facebook Hermes, published on 8 Oct 2020. 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-2020-1914 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hermes-engine (npm): affected all versions; fixed in 0.7.2\n- hermes-engine (npm): affected all versions; fixed in 0.7.2\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-1914/ (Markdown: https://insights.sbomify.com/CVE-2020-1914/index.md)","id":"CVE-2020-1914","markdown":"https://insights.sbomify.com/CVE-2020-1914/index.md","name":"CVE-2020-1914","record":{"aliases":["GHSA-327c-qx3v-h673"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript engine","requires_auth":"none","summary":"Attackers can read out-of-bounds memory or execute arbitrary code via crafted JavaScript in Hermes if untrusted script evaluation is permitted.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"hermes","vendor":"facebook"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"A logic vulnerability when handling the SaveGeneratorLong instruction in Facebook Hermes prior to commit b2021df620824627f5a8c96615edbd1eb7fdddfc allows attackers to potentially read out of bounds or theoretically execute arbitrary code via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits evaluation of untrusted JavaScript. Hence, most React Native applications are not affected.","ecosystems":["npm"],"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":"Always-Incorrect Control Flow Implementation in Facebook Hermes","id":"CVE-2020-1914","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Out-of-bounds Read in Facebook Hermes","id":"CVE-2020-1915"},"packages":[{"ecosystem":"npm","fixed":["0.7.2"],"introduced":["0"],"last_affected":[],"package":"hermes-engine","purl":null,"source":"GHSA-327c-qx3v-h673"},{"ecosystem":"npm","fixed":["0.7.2"],"introduced":["0"],"last_affected":[],"package":"hermes-engine","purl":"pkg:npm/hermes-engine","source":"GHSA-327c-qx3v-h673"}],"prev":{"headline":"Signed to Unsigned Conversion Error in Facebook Hermes","id":"CVE-2020-1913"},"products":["Hermes"],"published":"2020-10-08","related":[{"cvss_score":9.8,"headline":"Memory corruption in Hermes","id":"CVE-2023-23556","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"Memory corruption in Hermes","id":"CVE-2023-23557","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"Memory corruption in Hermes","id":"CVE-2023-25933","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"Use after free in Hermes","id":"CVE-2023-28081","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"Use after free in Hermes","id":"CVE-2023-30470","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"Memory corruption in Hermes","id":"CVE-2022-32234","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":9.8,"headline":"Integer overflow in Hermes","id":"CVE-2022-35289","kev_date_added":null,"published":"2022-10-11"}],"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":["Facebook"]},"summary":"Attackers can read out-of-bounds memory or execute arbitrary code via crafted JavaScript in Hermes if untrusted script evaluation is permitted.","url":"https://insights.sbomify.com/CVE-2020-1914/"}