Service token disclosure via insecure key storage
Published Jul 21, 2025 · Updated Jul 22, 2025
Hard-coded credentials in ASUS MyASUS 4.0.35.0 and earlier allow remote attackers to obtain a service-access token. The application stores a sensitive key insecurely, but ASUS has not identified the file, component, or operation that exposes it. The published network and privilege metrics indicate no authentication or user action is required, and the token enables communication with certain services.
Summary
What happened
Hard-coded credentials in ASUS MyASUS 4.0.35.0 and earlier allow remote attackers to obtain a service-access token. The application stores a sensitive key insecurely, but ASUS has not identified the file, component, or operation that exposes it. The published network and privilege metrics indicate no authentication or user action is required, and the token enables communication with certain services.
The record
- CVE
- CVE-2025-4569
- Published
- Jul 21, 2025
- Updated
- Jul 22, 2025
- Vendor
- ASUSTeK Computer Inc.
- Product
- MyASUS
- Classifications
- CWE-798, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0.35.0 and earlier
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo