Anchore Container Image ScannerApplication · Jenkins
CVE-2022-41225
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 · uneditedJenkins Anchore Container Image Scanner Plugin 1.0.24 and earlier does not escape content provided by the Anchore engine API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control API responses by Anchore engine.
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 confidenceThe Jenkins Anchore Container Image Scanner Plugin versions 1.0.24 and earlier fails to properly escape or sanitize content received from the Anchore engine API before rendering it in the Jenkins UI. This allows an attacker who can control the Anchore API responses to inject malicious scripts that execute in the browsers of users viewing the scan results, resulting in stored cross-site scripting (XSS).
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
Anchore Container Image ScannerApplication
< 1.0.25CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Verify Anchore Container Image Scanner Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Anchore Container Image Scanner' or check the plugin manifest file in the Jenkins plugins directoryAffected if Plugin is present in the Jenkins environment
-
Determine the installed plugin versionView the plugin details in Jenkins plugin manager or inspect the plugin's .hpi file metadataAffected if Version is 1.0.24 or earlier (any version below 1.0.25)
-
Confirm the plugin is configured and enabledCheck Jenkins job configurations or global Jenkins configuration for Anchore plugin settings; look for saved Anchore engine URL/credentials configurationsAffected if Plugin has an Anchore engine endpoint configured and is being used in CI/CD pipelines
User is affected if the Anchore Container Image Scanner Plugin version 1.0.24 or earlier is installed AND the plugin is configured with an Anchore engine connection, allowing potentially untrusted API responses to be rendered in the Jenkins UI.
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 · scoped1.0.25
Update to a patched version of the Anchore Container Image Scanner Plugin (if available) that properly escapes API response content before display. Until a patch is available, restrict access to trusted Anchore engines or disable the plugin.
Anchore Container Image Scanner Plugin version 1.0.25
- Navigate to Jenkins > Manage Jenkins > Manage Plugins
- Go to the 'Installed' tab and locate the Anchore Container Image Scanner plugin
- If an update is available, click 'Update now' to upgrade to version 1.0.25 or later
- Alternatively, download the latest version from the Jenkins plugin repository or the Anchore GitHub releases
- Restart Jenkins if required to complete the plugin update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Anchore Container Image Scanner
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41225 — 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-41225 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