{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-3462 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3462 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3462 is a high-severity missing authorization vulnerability in ASUS DriverHub, published on 9 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-3462 and fix it if it is affected.\n\nWhat it is: CVE-2025-3462 is a high-severity missing authorization vulnerability in ASUS DriverHub, published on 9 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-3462 in the wild and no public exploit code.\n\nAffected product: ASUS DriverHub. 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-3462/ (Markdown: https://insights.sbomify.com/CVE-2025-3462/index.md)","id":"CVE-2025-3462","markdown":"https://insights.sbomify.com/CVE-2025-3462/index.md","name":"CVE-2025-3462","record":{"aliases":["GHSA-584c-vcr8-r4h4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ASUS DriverHub","requires_auth":"none","summary":"Insufficient validation in ASUS DriverHub allows unauthorized sources to interact with software features via crafted HTTP requests on motherboards.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ASUS","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:H","version":"4.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"\"This issue is limited to motherboards and does not affect laptops, desktop computers, or other endpoints.\" An insufficient validation in ASUS DriverHub may allow unauthorized sources to interact with the software's features via crafted HTTP requests.\nRefer to the 'Security Update for ASUS DriverHub' section on the ASUS Security Advisory for more information.","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 DriverHub","id":"CVE-2025-3462","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Other in DriverHub","id":"CVE-2025-3463"},"packages":[],"prev":{"headline":"ON Semiconductor Quantenna Telnet Missing Authentication","id":"CVE-2025-3461"},"products":["DriverHub"],"published":"2025-05-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-19","vendors":["ASUS"]},"summary":"Insufficient validation in ASUS DriverHub allows unauthorized sources to interact with software features via crafted HTTP requests on motherboards.","url":"https://insights.sbomify.com/CVE-2025-3462/"}