dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-4569

HIGH · 7.7 CVSS v4.0 Published 2025-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An insecure sensitive key storage issue was found in MyASUS. potentially allowing unauthorized actor to obtain a token that could be used to communicate with certain services. Refer to the 'Security Update for for MyASUS' 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 confidence

Insecure storage of sensitive authentication tokens or keys within the MyASUS application allows a local attacker with certain access to potentially extract credentials. These credentials could then be used to impersonate legitimate users when communicating with ASUS backend services.

MitigationApply the official ASUS security update for MyASUS when available. Until then, limit local access to the affected system and monitor for unauthorized service usage.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MyASUS installation
    Check for MyASUS in the system program directory (e.g., C:\Program Files\ASUS\MyASUS or C:\Program Files (x86)\ASUS\MyASUS on Windows; /Applications/MyASUS on macOS). Also check the list of installed applications.
    Affected if MyASUS application is present on the system
  2. Locate MyASUS user data directory
    Navigate to the application data folder: %APPDATA%\MyASUS on Windows or ~/Library/Application Support/MyASUS on macOS. Inspect the folder structure for subdirectories containing configuration, cache, or storage folders.
    Affected if MyASUS user data directory exists and contains configuration files
  3. Identify credential storage files
    Search within the MyASUS data directory for files that may contain authentication data: look for files with extensions such as .json, .xml, .db, .sqlite, .ini, or .cfg. Pay particular attention to files with names containing 'token', 'auth', 'credential', 'login', or 'user'.
    Affected if Files potentially storing authentication tokens or keys are found in the MyASUS data directory
  4. Inspect file permissions
    Check the access permissions on identified credential storage files. On Windows, right-click the file, select Properties, then Security to view which users or groups have read access. On Unix-like systems, use 'ls -la' to view permissions.
    Affected if Files containing authentication data are readable by standard users or low-privilege accounts (other than the owner)
  5. Verify plaintext storage of sensitive tokens
    Open the identified credential files using a text editor or command-line tool (e.g., type, cat, or Get-Content). Examine the content for unencrypted authentication tokens, API keys, session tokens, or user credentials stored in plaintext.
    Affected if Authentication tokens, API keys, or user credentials are stored in plaintext (unencrypted) within readable files

If MyASUS is installed and stores authentication tokens or keys in files that are readable by non-privileged users, the environment is vulnerable to credential extraction via local access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the official ASUS security update for MyASUS when available. Until then, limit local access to the affected system and monitor for unauthorized service usage.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4569 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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