# CVE-2025-1533: Memory corruption in Armoury Crate

> A stack buffer overflow in the AsIO3.sys driver allows attackers to cause system crashes or potentially execute arbitrary code via input manipulation.

- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-3xrr-g3wm-x44g

## What is CVE-2025-1533?

CVE-2025-1533 is a high-severity memory corruption vulnerability in ASUS Armoury Crate, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack buffer overflow has been identified in the AsIO3.sys driver. This vulnerability can be triggered by input manipulation, may leading to a system crash (BSOD) or other potentially undefined execution.
Refer to the 'Security Update for Armoury Crate App' section on the ASUS Security Advisory for more information.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2025-1533 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1533 is a high-severity memory corruption vulnerability in ASUS Armoury Crate, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1533 in the wild and no public exploit code.

Affected product: ASUS Armoury Crate. 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-1533/ (Markdown: https://insights.sbomify.com/CVE-2025-1533/index.md)
```

## Sources

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

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