{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30135 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30135 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30135 is a critical missing authorization vulnerability in n/a, published on 25 Jul 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-30135 and fix it if it is affected.\n\nWhat it is: CVE-2025-30135 is a critical missing authorization vulnerability in n/a, published on 25 Jul 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-30135 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-30135/ (Markdown: https://insights.sbomify.com/CVE-2025-30135/index.md)","id":"CVE-2025-30135","markdown":"https://insights.sbomify.com/CVE-2025-30135/index.md","name":"CVE-2025-30135","record":{"aliases":["GHSA-fhfq-8mf9-qxmx"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IROAD Dashcam","requires_auth":"none","summary":"Attackers can access sensitive video recordings and live footage via HTTP and RTSP interfaces without authentication on IROAD Dashcam FX2 devices.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fx2_firmware","vendor":"iroadau"}],"cvss":{"score":9.4,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An issue was discovered on IROAD Dashcam FX2 devices. Dumping Files Over HTTP and RTSP Without Authentication can occur. It lacks authentication controls on its HTTP and RTSP interfaces, allowing attackers to retrieve sensitive files and video recordings. By connecting to http://192.168.10.1/mnt/extsd/event/, an attacker can download all stored video recordings in an unencrypted manner. Additionally, the RTSP stream on port 8554 is accessible without authentication, allowing an attacker to view live footage.","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":"Missing authorization in n/a","id":"CVE-2025-30135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30137"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-30133"},"products":["n/a"],"published":"2025-07-25","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2025-30133","kev_date_added":null,"published":"2025-07-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-30131","kev_date_added":null,"published":"2025-06-26"},{"cvss_score":5.3,"headline":"IROAD Dash Cam FX2 Device Registration default password","id":"CVE-2025-2347","kev_date_added":null,"published":"2025-03-16"},{"cvss_score":5.3,"headline":"IROAD Dash Cam FX2 HTTP/RTSP event information disclosure","id":"CVE-2025-2348","kev_date_added":null,"published":"2025-03-16"},{"cvss_score":5.3,"headline":"IROAD Dash Cam FX2 upload_file unrestricted upload","id":"CVE-2025-2350","kev_date_added":null,"published":"2025-03-16"},{"cvss_score":2.3,"headline":"IROAD Dash Cam FX2 Password Hash passwd weak password hash","id":"CVE-2025-2349","kev_date_added":null,"published":"2025-03-16"}],"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-07-25","vendors":["n/a"]},"summary":"Attackers can access sensitive video recordings and live footage via HTTP and RTSP interfaces without authentication on IROAD Dashcam FX2 devices.","url":"https://insights.sbomify.com/CVE-2025-30135/"}