AWS credential disclosure via embedded Docker files
Published Mar 5, 2025 · Updated Nov 3, 2025
Hard-coded credentials in Vasion Print before Application 20.0.2368 or Virtual Appliance Host 22.0.933 allow attackers to obtain AWS API keys. Docker image data embeds AWS access-key pairs in Readme.md, .env, and .env.local files, while Laravel configuration reads those values for S3 database backups. The disclosed keys were invalid when tested, so the demonstrated consequence is credential disclosure rather than confirmed AWS or Jenkins compromise.
Summary
What happened
Hard-coded credentials in Vasion Print before Application 20.0.2368 or Virtual Appliance Host 22.0.933 allow attackers to obtain AWS API keys. Docker image data embeds AWS access-key pairs in Readme.md, .env, and .env.local files, while Laravel configuration reads those values for S3 database backups. The disclosed keys were invalid when tested, so the demonstrated consequence is credential disclosure rather than confirmed AWS or Jenkins compromise.
The record
- CVE
- CVE-2025-27643
- Published
- Mar 5, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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