{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30113 is a critical 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-30113 and fix it if it is affected.\n\nWhat it is: CVE-2025-30113 is a critical 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-30113 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-30113/ (Markdown: https://insights.sbomify.com/CVE-2025-30113/index.md)","id":"CVE-2025-30113","markdown":"https://insights.sbomify.com/CVE-2025-30113/index.md","name":"CVE-2025-30113","record":{"aliases":["GHSA-5rfm-vp96-44gv"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"dashcam","requires_auth":"none","summary":"Hardcoded credentials in the dashcam's Android app allow unauthorized network access to device settings and data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dr_820_firmware","vendor":"hella"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on the Forvia Hella HELLA Driving Recorder DR 820. Hardcoded Credentials exist in the APK for Ports 9091 and 9092. The dashcam's Android application contains hardcoded credentials that allow unauthorized access to device settings through ports 9091 and 9092. These credentials, stored in cleartext, can be exploited by an attacker who gains access to the dashcam's network.","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":"Hardcoded credentials in n/a","id":"CVE-2025-30113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-30114"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-30112"},"products":["n/a"],"published":"2025-03-18","related":[{"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"},{"cvss_score":7.3,"headline":"Auth bypass in n/a","id":"CVE-2025-30117","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":"total"},"state":"PUBLISHED","updated":"2025-03-21","vendors":["n/a"]},"summary":"Hardcoded credentials in the dashcam's Android app allow unauthorized network access to device settings and data.","url":"https://insights.sbomify.com/CVE-2025-30113/"}