{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-25733 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25733 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25733 is a low-severity missing authorization vulnerability in n/a, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25733 and fix it if it is affected.\n\nWhat it is: CVE-2025-25733 is a low-severity missing authorization vulnerability in n/a, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25733 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-25733/ (Markdown: https://insights.sbomify.com/CVE-2025-25733/index.md)","id":"CVE-2025-25733","markdown":"https://insights.sbomify.com/CVE-2025-25733/index.md","name":"CVE-2025-25733","record":{"aliases":["GHSA-mhw2-47hc-23pg"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Roadside Unit","requires_auth":"none","summary":"Physically proximate attackers can arbitrarily modify SPI flash regions in Kapsch TrafficCom Roadside Units due to incorrect access control, degrading device security.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ris-9160_firmware","vendor":"kapsch"},{"product":"ris-9260_firmware","vendor":"kapsch"}],"cvss":{"score":3.5,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1233","name":"Security-Sensitive Hardware Controls with Missing Lock Bit Protection"}],"description":"Incorrect access control in the SPI Flash Chip of Kapsch TrafficCom RIS-9160 \u0026 RIS-9260 Roadside Units (RSUs) v3.2.0.829.23, v3.8.0.1119.42, and v4.6.0.1211.28 allows physically proximate attackers to arbitrarily modify SPI flash regions, leading to a degradation of the security posture of the device.","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-25733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-25734"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-25732"},"products":["n/a"],"published":"2025-08-26","related":[{"cvss_score":6.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-25732","kev_date_added":null,"published":"2025-08-26"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2025-25734","kev_date_added":null,"published":"2025-08-26"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2025-25736","kev_date_added":null,"published":"2025-08-26"},{"cvss_score":6.8,"headline":"Weak cryptography in n/a","id":"CVE-2025-25737","kev_date_added":null,"published":"2025-08-26"},{"cvss_score":4.6,"headline":"Security feature bypass in n/a","id":"CVE-2025-25735","kev_date_added":null,"published":"2025-08-26"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-22","vendors":["n/a"]},"summary":"Physically proximate attackers can arbitrarily modify SPI flash regions in Kapsch TrafficCom Roadside Units due to incorrect access control, degrading device security.","url":"https://insights.sbomify.com/CVE-2025-25733/"}