CVE-2024-12957
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2024-12957 is a file handling command vulnerability in ASUS Armoury Crate software that allows arbitrary file deletion due to improper input validation in file handling operations. An attacker with local access could potentially exploit this to delete critical system or user files, leading to denial of service or further compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Armoury Crate is installedOpen Windows Settings > Apps > Apps & Features and search for 'Armoury Crate' or open Control Panel > Programs and Features. Alternatively, check for the installation at C:\Program Files\ASUS\Armoury Crate\ or look for the Armoury Crate service in Services.mscAffected if Armoury Crate is not installed on the system
-
Identify the installed versionRight-click on the Armoury Crate shortcut (if available) and select Properties, or open the application and navigate to Settings > About. The version number is typically displayed in the format x.x.x.xAffected if The installed version is older than the patched version released 01/23/2025 or cannot be determined from the application UI
-
Check for the Armoury Crate serviceOpen Services.msc and look for a service related to Armoury Crate (such as 'Armoury Crate Service' or 'ASUS Armoury Crate'). Verify if the service is runningAffected if The Armoury Crate service is running and the version cannot be confirmed as patched
-
Review file handling permissionsExamine the permissions on the Armoury Crate installation directory (C:\Program Files\ASUS\Armoury Crate\) and check if the user account has write access to system directories. The vulnerability requires the file handling feature to process user-supplied file pathsAffected if Armoury Crate is installed with the file handling or lighting control features enabled and the service runs with elevated privileges
If Armoury Crate is installed and the installed version is older than the 01/23/2025 patch, the system is likely affected by this arbitrary file deletion vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the security update for Armoury Crate released on 01/23/2025 as specified in the ASUS Security Advisory. Verify all affected installations are patched to a version that includes the fix.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12957 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data