Pipeline\Application · Jenkins
CVE-2022-43409
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 Pipeline: Supporting APIs Plugin 838.va_3a_087b_4055b and earlier does not sanitize or properly encode URLs of hyperlinks sending POST requests in build logs, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create Pipelines.
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 Pipeline: Supporting APIs Plugin fails to sanitize or properly encode URLs in hyperlinks that send POST requests when rendering them in build logs. This allows stored XSS injection through malicious URLs in Pipeline definitions, exploitable by attackers with Pipeline creation permissions.
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
Pipeline\Application
<= 838.va_3a_087b_4055bCVSS 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.
-
Check the Pipeline: Supporting APIs Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Supporting APIs' to view the installed version numberAffected if The installed version is 838.va_3a_087b_4055b or lower
-
Confirm Pipeline creation permissions existNavigate to Jenkins > Manage Jenkins > Manage Users and review which users have the ability to create or configure Pipelines, or check Job/Overall/Read permissions in the security matrixAffected if Users other than trusted administrators have Pipeline creation or configuration permissions
-
Inspect recent build logs for hyperlinks with unusual URLsView build logs from recent Pipeline builds and examine any hyperlinks rendered within the logs - look for URLs that contain suspicious characters or unexpected domainsAffected if Build logs contain hyperlinks with encoded characters, JavaScript handlers, or URLs pointing to unexpected domains
You are affected if the Pipeline: Supporting APIs Plugin version is 838.va_3a_087b_4055b or lower AND users with Pipeline creation permissions exist in your environment.
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 · scopedUpdate the Jenkins Pipeline: Supporting APIs Plugin to a version later than 838.va_3a_087b_4055b. Until the patch is applied, limit Pipeline creation permissions to trusted users only and exercise caution when viewing build logs.
Pipeline: Supporting APIs Plugin (workflow-support) version 848.v8a_6e400d9c24 or later
- 1. Navigate to Jenkins dashboard
- 2. Go to Manage Jenkins > Manage Plugins
- 3. Click on the 'Updates' tab
- 4. Look for 'Pipeline: Supporting APIs' plugin (workflow-support)
- 5. If an update is available, select the plugin and click 'Download now and install after restart'
- 6. Alternatively, download the plugin from the Jenkins plugin repository and upload it manually via 'Advanced' > 'Upload Plugin'
- 7. Restart Jenkins after the update completes
- 8. Verify the plugin version is greater than 838.va_3a_087b_4055b
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43409 — 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-43409 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