WaltiApplication · Jenkins
CVE-2022-41240
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 Walti Plugin 1.0.1 and earlier does not escape the information provided by the Walti API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide malicious API responses from Walti.
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 · moderate confidenceThe Jenkins Walti Plugin versions 1.0.1 and earlier contain a stored cross-site scripting (XSS) vulnerability due to improper escaping of data returned by the Walti API. Attackers who can control or manipulate the Walti API responses can inject malicious JavaScript that executes in the browsers of users viewing the plugin's output.
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
WaltiApplication
<= 1.0.1CVSS 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 Walti Plugin is installedGo to Manage Jenkins > Manage Plugins > Installed and search for 'Walti' or check the plugin directory $JENKINS_HOME/plugins for the walti plugin folderAffected if The Walti plugin is present in the Jenkins instance
-
Check installed Walti Plugin versionIn Manage Jenkins > Manage Plugins > Installed, find the Walti plugin and note the version number. Compare it to the affected range: 1.0.1 and earlierAffected if The installed version is 1.0.1 or any version lower than 1.0.1
-
Determine if plugin is configured with a Walti API endpointGo to Manage Jenkins > Configure System and look for Walti configuration section. Check if a Walti API URL/endpoint is configuredAffected if A Walti API endpoint is configured and the plugin is actively fetching data from it
-
Check if users can access Walti plugin outputReview Jenkins permissions (Manage Jenkins > Configure Global Security > Authorization) to see which users or groups can view job pages or build outputs where Walti data is displayedAffected if Users other than administrators can access pages displaying Walti plugin results
You are affected if the Walti plugin version is 1.0.1 or earlier AND a Walti API is configured AND users can view the plugin output in their browsers.
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.
From vendor dataUpdate the Jenkins Walti Plugin to the latest version (greater than 1.0.1) which properly escapes/sanitizes all API response data before rendering. If no update is available, implement output encoding for all Walti API data displayed in the Jenkins interface.
Fix this in Walti
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41240 — 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-41240 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