{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30140 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30140 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30140 is a high-severity 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-30140 and fix it if it is affected.\n\nWhat it is: CVE-2025-30140 is a high-severity 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-30140 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-30140/ (Markdown: https://insights.sbomify.com/CVE-2025-30140/index.md)","id":"CVE-2025-30140","markdown":"https://insights.sbomify.com/CVE-2025-30140/index.md","name":"CVE-2025-30140","record":{"aliases":["GHSA-f2hc-7f9p-xfqm"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"G-Net Dashcam","requires_auth":"none","summary":"Attackers can register an unowned internal domain to intercept dashcam traffic, enabling data exfiltration or man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"g-onx_firmware","vendor":"gnetsystem"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered on G-Net Dashcam BB GONX devices. A Public Domain name is Used for the Internal Domain Name. It uses an unregistered public domain name as an internal domain, creating a security risk. This domain was not owned by GNET originally, allowing an attacker to register it and potentially intercept sensitive device traffic (it has since been registered by the vulnerability discoverer). If the dashcam or related services attempt to resolve this domain over the public Internet instead of locally, it could lead to data exfiltration or man-in-the-middle attacks.","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":"Misconfiguration in n/a","id":"CVE-2025-30140","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-30141"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30139"},"products":["n/a"],"published":"2025-03-18","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-30139","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2025-30142","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2025-30141","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":4.6,"headline":"Missing authorization in n/a","id":"CVE-2025-30138","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 can register an unowned internal domain to intercept dashcam traffic, enabling data exfiltration or man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2025-30140/"}