Credential disclosure via SBOM credential embedding
Published Jul 20, 2022 · Updated Sep 16, 2024
Credential exposure in AnchoreCTL 0.1.4 allows attackers to obtain Anchore Enterprise API credentials from generated SBOMs. During SBOM generation, the client writes the API credentials used for Enterprise access into the resulting SBOM instead of excluding secrets. Exposure requires access to an affected client-produced SBOM, and disclosed credentials permit the API access granted to the embedded account.
Summary
What happened
Credential exposure in AnchoreCTL 0.1.4 allows attackers to obtain Anchore Enterprise API credentials from generated SBOMs. During SBOM generation, the client writes the API credentials used for Enterprise access into the resulting SBOM instead of excluding secrets. Exposure requires access to an affected client-produced SBOM, and disclosed credentials permit the API access granted to the embedded account.
The record
- CVE
- CVE-2022-1766
- Published
- Jul 20, 2022
- Updated
- Sep 16, 2024
- Vendor
- Anchore
- Product
- Anchore Enterprise
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=unspecified <4.0.1
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