AWS credential disclosure via plaintext repository embedding
Published Jun 26, 2025 · Updated Jun 27, 2025
Missing encryption in git-annex 3.20121126 through 5.20140918 allows attackers to extract embedded AWS credentials from a repository copy. The S3 and Glacier remote setup path stores credentials effectively as plaintext when embedcreds=yes is combined with encryption=pubkey or encryption=hybrid. Exposure requires that configuration and access to a repository copy; it discloses the AWS keys without granting direct repository modification or service interruption.
Summary
What happened
Missing encryption in git-annex 3.20121126 through 5.20140918 allows attackers to extract embedded AWS credentials from a repository copy. The S3 and Glacier remote setup path stores credentials effectively as plaintext when embedcreds=yes is combined with encryption=pubkey or encryption=hybrid. Exposure requires that configuration and access to a repository copy; it discloses the AWS keys without granting direct repository modification or service interruption.
The record
- CVE
- CVE-2014-6274
- Published
- Jun 26, 2025
- Updated
- Jun 27, 2025
- Vendor
- git-annex
- Product
- git-annex
- Classifications
- CWE-311, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2025CVE publishedPublication date reported by the CVE source.
- Jun 27, 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=3.20121126 <5.20140919
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