{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30133 exists.","fix":"No fix has been published for CVE-2025-30133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30133 is a critical authentication bypass vulnerability in n/a, published on 28 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-30133 and fix it if it is affected.\n\nWhat it is: CVE-2025-30133 is a critical authentication bypass vulnerability in n/a, published on 28 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30133 exists.\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-30133/ (Markdown: https://insights.sbomify.com/CVE-2025-30133/index.md)","id":"CVE-2025-30133","markdown":"https://insights.sbomify.com/CVE-2025-30133/index.md","name":"CVE-2025-30133","record":{"aliases":["GHSA-v9v8-8vjh-j435"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IROAD Dashcam","requires_auth":"none","summary":"Attackers can bypass device pairing and silently access the dashcam's HTTP server via its Wi-Fi network without authentication.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fx2_firmware","vendor":"iroadau"}],"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-284","name":"Improper Access Control"}],"description":"An issue was discovered on IROAD Dashcam FX2 devices. Bypass of Device Pairing/Registration can occur. It requires device registration via the \"IROAD X View\" app for authentication, but its HTTP server lacks this restriction. Once connected to the dashcam's Wi-Fi network via the default password (\"qwertyuiop\"), an attacker can directly access the HTTP server at http://192.168.10.1 without undergoing the pairing process. Additionally, no alert is triggered on the device when an attacker connects, making this intrusion completely silent.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-30133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-30135"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2025-30132"},"products":["n/a"],"published":"2025-07-28","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-30131","kev_date_added":null,"published":"2025-06-26"},{"cvss_score":9.4,"headline":"Missing authorization in n/a","id":"CVE-2025-30135","kev_date_added":null,"published":"2025-07-25"},{"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-30","vendors":["n/a"]},"summary":"Attackers can bypass device pairing and silently access the dashcam's HTTP server via its Wi-Fi network without authentication.","url":"https://insights.sbomify.com/CVE-2025-30133/"}