CVE-2025-4569
ASUS MyASUS Token Stealing Vulnerability
Description
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.
INFO
Published Date :
July 21, 2025, 8:15 a.m.
Last Modified :
July 22, 2025, 1:06 p.m.
Remotely Exploit :
Yes !
Source :
54bf65a7-a193-42d2-b1ba-8e150d3c35e1
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 54bf65a7-a193-42d2-b1ba-8e150d3c35e1 |
Solution
- Update MyASUS to the latest version.
- Review ASUS Security Advisory for key storage details.
- Implement secure key storage mechanisms.
- Restrict access to sensitive service tokens.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-4569.
| URL | Resource |
|---|---|
| https://www.asus.com/content/security-advisory/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-4569 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-4569
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-4569 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-4569 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 54bf65a7-a193-42d2-b1ba-8e150d3c35e1
Jul. 21, 2025
Action Type Old Value New Value Added Reference https://www.asus.com/content/security-advisory/ Removed Reference https://www.asus.com/content/asus-product-security-advisory/ -
New CVE Received by 54bf65a7-a193-42d2-b1ba-8e150d3c35e1
Jul. 21, 2025
Action Type Old Value New Value Added Description 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. Added CVSS V4.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 Added CWE CWE-798 Added Reference https://www.asus.com/content/asus-product-security-advisory/