{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2022-27948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27948 is a high-severity vulnerability in n/a, published on 27 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-27948 and fix it if it is affected.\n\nWhat it is: CVE-2022-27948 is a high-severity vulnerability in n/a, published on 27 Mar 2022. 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-2022-27948 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-27948/ (Markdown: https://insights.sbomify.com/CVE-2022-27948/index.md)","id":"CVE-2022-27948","markdown":"https://insights.sbomify.com/CVE-2022-27948/index.md","name":"CVE-2022-27948","record":{"aliases":["GHSA-65jp-cf4c-rcq6"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Tesla vehicle","requires_auth":"none","summary":"Attackers can open Tesla charging ports using a replayed RF signal, bypassing intended access controls, though the vendor considers this behavior intended.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"model_3_firmware","vendor":"tesla"},{"product":"model_s_firmware","vendor":"tesla"},{"product":"model_x_firmware","vendor":"tesla"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:L/C:N/I:L/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Certain Tesla vehicles through 2022-03-26 allow attackers to open the charging port via a 315 MHz RF signal containing a fixed sequence of approximately one hundred symbols. NOTE: the vendor's perspective is that the behavior is as intended","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2022-27948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Airflow prior to 2.3.1 may include sensitive values in rendered template","id":"CVE-2022-27949"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-27947"},"products":["n/a"],"published":"2022-03-27","related":[{"cvss_score":9,"headline":"Tesla Model 3 Gateway Firmware Signature Validation Bypass Vulnerability","id":"CVE-2023-32156","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.8,"headline":"Use after free in Model 3","id":"CVE-2022-42430","kev_date_added":null,"published":"2023-03-29"},{"cvss_score":8.8,"headline":"Memory corruption in Model 3","id":"CVE-2022-42431","kev_date_added":null,"published":"2023-03-29"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2019-9977","kev_date_added":null,"published":"2019-03-24"},{"cvss_score":7.8,"headline":"Tesla Model 3 bcmdhd Out-Of-Bounds Write Local Privilege Escalation Vulnerability","id":"CVE-2023-32155","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":7.6,"headline":"Code injection in Model 3","id":"CVE-2022-3093","kev_date_added":null,"published":"2023-03-29"},{"cvss_score":7.5,"headline":"Tesla Model 3 VCSEC Integer Overflow Remote Code Execution Vulnerability","id":"CVE-2025-2082","kev_date_added":null,"published":"2025-04-30"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can open Tesla charging ports using a replayed RF signal, bypassing intended access controls, though the vendor considers this behavior intended.","url":"https://insights.sbomify.com/CVE-2022-27948/"}