JenkinsApplication
CVE-2022-41224
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 2.367 through 2.369 (both inclusive) does not escape tooltips of the l:helpIcon UI component used for some help icons on the Jenkins web UI, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control tooltips for this component.
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 confidenceJenkins versions 2.367 through 2.369 contain a stored XSS vulnerability in the l:helpIcon UI component where tooltips are not properly escaped, allowing attackers with control over tooltip content to inject malicious JavaScript that executes when users view the affected help icons.
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
JenkinsApplication
>= 2.367, < 2.370CVSS 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.
-
Determine installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /whoAmI/api/json endpoint, or run 'java -jar jenkins.war --version' if you have CLI accessAffected if Version is 2.367, 2.368, or 2.369 (any version >= 2.367 and < 2.370)
-
Verify l:helpIcon component usageSearch Jenkins core and installed plugins for usage of the l:helpIcon Jelly tag, looking for instances where tooltip attribute contains dynamic contentAffected if The l:helpIcon tag is used with a tooltip parameter that accepts user-supplied or dynamically constructed content
-
Check for custom plugins or scripts injecting help tooltip contentReview custom plugins, build scripts, or configuration that populates help tooltips, particularly those accepting user input or external dataAffected if Custom code or plugins inject unsanitized content into the tooltip attribute of help icons
Your environment is affected if Jenkins version is 2.367, 2.368, or 2.369 AND the l:helpIcon component is used with user-controlled tooltip content.
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 · scoped2.370
Upgrade Jenkins to version 2.370 or later to receive the patch that properly escapes tooltip content in the l:helpIcon component.
Jenkins 2.370 or later
- Back up your Jenkins home directory and configuration before upgrading
- Download Jenkins 2.370 or later from the official Jenkins releases page (https://www.jenkins.io/download/)
- Stop the Jenkins service
- Upgrade Jenkins to version 2.370 or later using your preferred installation method (war file, package manager, or Docker)
- Start the Jenkins service
- Verify the upgrade was successful by checking the Jenkins version at /about/
- Confirm the vulnerability is remediated by testing that help icon tooltips are properly escaped
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41224 — 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-41224 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