Repository credential exposure via Docker build context
Published Apr 4, 2025 · Updated Apr 4, 2025
Credential exposure in acme.sh Docker images before 40b6db6 allows remote attackers to read and misuse a persisted repository token. The Docker Hub workflow lets actions/checkout write its authentication token into local Git configuration, and the Dockerfile copies the entire checkout into the image build. Exploitation requires access to an affected image or layer while the token is valid, enabling repository data access or modification rather than service interruption.
Summary
What happened
Credential exposure in acme.sh Docker images before 40b6db6 allows remote attackers to read and misuse a persisted repository token. The Docker Hub workflow lets actions/checkout write its authentication token into local Git configuration, and the Dockerfile copies the entire checkout into the image build. Exploitation requires access to an affected image or layer while the token is valid, enabling repository data access or modification rather than service interruption.
The record
- CVE
- CVE-2025-32111
- Published
- Apr 4, 2025
- Updated
- Apr 4, 2025
- Vendor
- acme.sh Project
- Product
- acme.sh
- Classifications
- CWE-260, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2025CVE publishedPublication date reported by the CVE source.
- Apr 4, 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=0 <40b6db6a2715628aa977ed1853fe5256704010ae
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.
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