# CVE-2024-12957: Missing authorization in Armoury Crate

> An attacker can delete arbitrary files due to missing authentication in ASUS Armoury Crate, requiring users to apply the latest security update.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-c3fr-pjq5-rf6r

## What is CVE-2024-12957?

CVE-2024-12957 is a high-severity missing authorization vulnerability in ASUS Armoury Crate, published on 23 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A file handling command vulnerability in certain versions of Armoury Crate may result in arbitrary file deletion.
Refer to the '01/23/2025 Security Update for Armoury Crate App' section on the ASUS Security Advisory for more information.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-12957?


## How do I fix CVE-2024-12957?

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

## Is CVE-2024-12957 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12957 and fix it if it is affected.

What it is: CVE-2024-12957 is a high-severity missing authorization vulnerability in ASUS Armoury Crate, published on 23 Jan 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-2024-12957 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-2024-12957/ (Markdown: https://insights.sbomify.com/CVE-2024-12957/index.md)
```

## Sources

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

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