Anchore Enterprise: Insufficiently Protected Credentials
CVE-2022-1766 is a high-severity insufficiently protected credentials vulnerability in Anchore Enterprise from Anchore, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.0.1 as the first without the flaw, so updating Anchore Enterprise to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.7% chance of exploitation within 30 days, higher than 54% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Anchore Enterprise to 4.0.1 or a later version.
- Update AnchoreCTL to 0.1.5 or a later version.
- Update Anchore to 4.0.1 or a later version.
- Read the advisory on docs.anchore.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Anchore | Anchore Enterprise | before 4.0.1 | 4.0.1 |
| Anchore | AnchoreCTL | before 0.1.5 | 0.1.5 |
| Anchore | Anchore | before 4.0.1 | 4.0.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
Official description
Anchore Enterprise anchorectl version 0.1.4 improperly stored credentials when generating a Software Bill of Materials. anchorectl will add the credentials used to access Anchore Enterprise API in the Software Bill of Materials (SBOM) generated by anchorectl. Users of anchorectl version 0.1.4 should upgrade to anchorectl version 0.1.5 to resolve this issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
How developers prevent this class of flaw
- Use an appropriate security mechanism to protect the credentials.
- Make appropriate use of cryptography to protect the credentials.
- Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
More Insufficiently Protected Credentials vulnerabilities (CWE-522)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- docs.anchore.com/current/docs/releasenotes/401/Release Notes
Other vulnerabilities in Anchore Enterprise
- 8.8 High severity
- 7.3 High severity
Recent Insufficiently Protected Credentials vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.