CVE-2022-1766
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAnchore 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceanchorectl version 0.1.4 improperly includes Anchore Enterprise API credentials in the Software Bill of Materials (SBOM) output it generates, leading to credential exposure in plaintext within the SBOM file. This is an information disclosure vulnerability where authentication credentials are inadvertently persisted in a file intended for software inventory purposes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.0.1< 0.1.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check anchorectl versionRun 'anchorectl --version' or 'anchorectl version' to determine the installed versionAffected if The version is 0.1.4 or earlier (versions below 0.1.5 are affected)
-
Locate generated SBOM filesSearch for SBOM output files (commonly named with .json, .spdx, .cyclonedx extensions, or containing 'sbom' in the filename) in directories where anchorectl was runAffected if SBOM files exist and were generated using an affected anchorectl version
-
Inspect SBOM files for credentialsOpen SBOM files in a text editor or use 'grep -i' to search for strings resembling API keys, passwords, tokens, or auth credentials (look for keywords like 'password', 'api_key', 'token', 'secret', 'credential', or base64-encoded strings that may appear as values)Affected if Plaintext credentials, API keys, tokens, or authentication strings are found within the SBOM content
You are affected if anchorectl version 0.1.4 was used to generate SBOM files that now contain exposed credentials in plaintext.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.1.54.0.1
Upgrade anchorectl from version 0.1.4 to version 0.1.5 to prevent credentials from being written to SBOMs. Additionally, rotate any credentials that may have been used with the affected version, as they may have been exposed in generated SBOM files.
anchorectl version 0.1.5
- Upgrade anchorectl to version 0.1.5 or later by downloading the latest release from the official Anchore repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data