Credential disclosure via hard-coded AES token secret
Published Sep 8, 2025 · Updated Sep 8, 2025
Hard-coded key use in the Datart API 1.0.0-rc1 through 1.0.0-rc3 allows remote authenticated users to decrypt stored credentials. AESUtil.getTokensecret returns a constant secret that encrypts password values exposed by the data-source API, so the same key decrypts every response. A low-privileged account and access to a data-source response are required; disclosure is limited to the returned account, server, and password data.
Summary
What happened
Hard-coded key use in the Datart API 1.0.0-rc1 through 1.0.0-rc3 allows remote authenticated users to decrypt stored credentials. AESUtil.getTokensecret returns a constant secret that encrypts password values exposed by the data-source API, so the same key decrypts every response. A low-privileged account and access to a data-source response are required; disclosure is limited to the returned account, server, and password data.
The record
- CVE
- CVE-2025-10080
- Published
- Sep 8, 2025
- Updated
- Sep 8, 2025
- Vendor
- running-elephant
- Product
- Datart
- Classifications
- CWE-320, CWE-321, T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 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=1.0.0-rc1
- Affected versionversion=1.0.0-rc2
- Affected versionversion=1.0.0-rc3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Elephant-Datart information disclosure reproductionproof of concept · demonstrated
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