{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30117 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30117 is a high-severity authentication bypass vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30117 and fix it if it is affected.\n\nWhat it is: CVE-2025-30117 is a high-severity authentication bypass vulnerability in n/a, published on 18 Mar 2025. 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-2025-30117 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-2025-30117/ (Markdown: https://insights.sbomify.com/CVE-2025-30117/index.md)","id":"CVE-2025-30117","markdown":"https://insights.sbomify.com/CVE-2025-30117/index.md","name":"CVE-2025-30117","record":{"aliases":["GHSA-qvq7-g7xm-xr5h"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"vehicle dashcam","requires_auth":"none","summary":"Attackers bypass device pairing to access sensitive data and modify power settings, causing battery drainage and disabling recording on the dashcam.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dr_820_firmware","vendor":"hella"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"An issue was discovered on the Forvia Hella HELLA Driving Recorder DR 820. Managing Settings and Obtaining Sensitive Data and Sabotaging the Car Battery can be performed by unauthorized parties. After bypassing the device pairing, an attacker can obtain sensitive user and vehicle information through the settings interface. Remote attackers can modify power management settings, disable recording, delete stored footage, and turn off battery protection, leading to potential denial-of-service conditions and vehicle battery drainage.","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":"Auth bypass in n/a","id":"CVE-2025-30117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30118"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-30116"},"products":["n/a"],"published":"2025-03-18","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30113","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30115","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":9.1,"headline":"Auth bypass in n/a","id":"CVE-2025-30114","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2025-30116","kev_date_added":null,"published":"2025-03-18"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["n/a"]},"summary":"Attackers bypass device pairing to access sensitive data and modify power settings, causing battery drainage and disabling recording on the dashcam.","url":"https://insights.sbomify.com/CVE-2025-30117/"}