Security readout for executives and security teams
Plain-English summary
Anchorectl 0.1.4 could place Anchore Enterprise API credentials inside SBOMs it generated. If those SBOMs were shared, uploaded, or archived, the credentials may have been exposed outside the intended system. The stated fix is upgrading anchorectl to 0.1.5.
Executive priority
Treat this as a credential exposure cleanup item. Prioritize if SBOMs are shared externally, stored in CI artifacts, or accessible to many users. Upgrade and credential rotation should be completed promptly, but available sources do not support claims of active exploitation.
Technical view
CVE-2022-1766 is a CWE-522 credential storage issue in Anchore Enterprise anchorectl 0.1.4. During SBOM generation, anchorectl added credentials used for Anchore Enterprise API access into the generated SBOM. Public sources do not provide CVSS scoring or broader affected version detail.
Likely exposure
Exposure is likely limited to organizations that used anchorectl 0.1.4 to generate SBOMs against Anchore Enterprise. Risk depends on where those SBOMs were stored, published, emailed, or uploaded, and whether the embedded API credentials remained valid.
Exploitation context
The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. Practical risk comes from accidental credential disclosure through SBOM distribution or artifact storage, not from a described remote exploit path.
Researcher notes
Evidence is concise: affected behavior is described for anchorectl 0.1.4, and upgrade to 0.1.5 is named as the resolution. No CVSS vector, exploit details, or exact credential fields are provided in the source bundle.
Mitigation direction
- Upgrade anchorectl from 0.1.4 to 0.1.5 or later.
- Rotate Anchore Enterprise API credentials used with anchorectl 0.1.4.
- Restrict access to SBOM storage and distribution locations.
- Remove or replace SBOMs confirmed to contain credentials.
- Check Anchore release notes for any additional vendor guidance.
Validation and detection
- Identify any systems using anchorectl version 0.1.4.
- Inventory SBOMs generated during anchorectl 0.1.4 usage.
- Review affected SBOMs for unintended Anchore Enterprise API credentials.
- Confirm anchorectl reports version 0.1.5 or later.
- Verify exposed credentials were revoked or rotated.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-522: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-1766 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.anchore.com/current/docs/releasenotes/401/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficiently Protected Credentials
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.