{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2022-37418 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-37418 is a medium-severity vulnerability in n/a, published on 24 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-37418 and fix it if it is affected.\n\nWhat it is: CVE-2022-37418 is a medium-severity vulnerability in n/a, published on 24 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-37418 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-2022-37418/ (Markdown: https://insights.sbomify.com/CVE-2022-37418/index.md)","id":"CVE-2022-37418","markdown":"https://insights.sbomify.com/CVE-2022-37418/index.md","name":"CVE-2022-37418","record":{"aliases":["GHSA-85q8-mjfv-gjfx"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vehicle RKE system","requires_auth":"none","summary":"Attackers can bypass vehicle security to unlock cars indefinitely by capturing and replaying key fob signals via a RollBack attack.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hyundai_firmware","vendor":"hyundai"},{"product":"kia_firmware","vendor":"kia"},{"product":"nissan_firmware","vendor":"nissan"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"The Remote Keyless Entry (RKE) receiving unit on certain Nissan, Kia, and Hyundai vehicles through 2017 allows remote attackers to perform unlock operations and force a resynchronization after capturing two consecutive valid key fob signals over the radio, aka a RollBack attack. The attacker retains the ability to unlock indefinitely.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-08-14","github_poc":1,"max_poc_stars":10,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-14T11:45:46Z","kind":"github_poc","ref":"https://github.com/thomasarmel/rollback_car_attack_proverif","stars":10,"title":"ProVerif proof of concept of the Rollback attack on car keyfob (CVE-2022-37418, CVE-2022-36945 and CVE-2022-37305)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2022-37418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Silverstipe CMS Stored XSS in custom meta tags","id":"CVE-2022-37421"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-37416"},"products":["n/a"],"published":"2022-08-24","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can bypass vehicle security to unlock cars indefinitely by capturing and replaying key fob signals via a RollBack attack.","url":"https://insights.sbomify.com/CVE-2022-37418/"}