# CVE-2025-3463: Other in DriverHub

> Insufficient validation in ASUS DriverHub allows untrusted sources to affect system behavior via crafted HTTP requests on motherboards.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-mh97-9pr7-97ww

## What is CVE-2025-3463?

CVE-2025-3463 is a critical 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.

### Official description

"This issue is limited to motherboards and does not affect laptops, desktop computers, or other endpoints." An insufficient validation vulnerability in ASUS DriverHub may allow untrusted sources to affect system behavior via crafted HTTP requests.
Refer to the 'Security Update for ASUS DriverHub' section on the ASUS Security Advisory for more information.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-3463?


## How do I fix CVE-2025-3463?

No fix has been published for CVE-2025-3463 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3463 being exploited?

There is no known exploitation of CVE-2025-3463 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3463 and fix it if it is affected.

What it is: CVE-2025-3463 is a critical 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.
Exploitation: There is no known exploitation of CVE-2025-3463 in the wild and no public exploit code.

Affected product: ASUS DriverHub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3463/ (Markdown: https://insights.sbomify.com/CVE-2025-3463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3463
- OSV: https://osv.dev/vulnerability/CVE-2025-3463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3463/
Summaries are generated and may contain mistakes; the official description above is the record.