dbcve.org
DotciApplication · Jenkins

CVE-2022-41239

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 2.40.00 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins DotCi Plugin 2.40.00 and earlier does not escape the GitHub user name parameter provided to commit notifications when displaying them in a build cause, resulting in a stored cross-site scripting (XSS) vulnerability.

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 confidence

The Jenkins DotCi Plugin versions 2.40.00 and earlier fail to properly escape the GitHub username parameter from commit notifications when rendering them in the build cause display, allowing stored XSS injection via malicious JavaScript embedded in the username.

MitigationUpdate the DotCi Plugin to version 2.40.01 or later which implements proper output encoding for the GitHub username field, or apply input validation on commit notification parameters before display.

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
DotciApplication
Affected:<= 2.40.00

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify DotCi plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'DotCi', or execute: Jenkins.instance.pluginManager.getPlugin('dotci') via the script console
    Affected if DotCi plugin is not found in the installed plugins list, then the vulnerability does not apply
  2. Check installed DotCi version
    In the plugin manager Installed tab, note the version column for DotCi. Or via script console: Jenkins.instance.pluginManager.getPlugin('dotci').getVersion()
    Affected if Version is 2.40.00 or earlier (any version <= 2.40.00)
  3. Verify GitHub integration is configured
    Check if DotCi is configured with a GitHub repository. Go to job configuration > look for DotCi settings, or check if the job receives webhooks from GitHub. The vulnerable code path is triggered when GitHub commit notifications with username data are processed
    Affected if GitHub is integrated and commit notifications are being received by Jenkins jobs using DotCi
  4. Inspect build cause display for unescaped content
    View a completed build that received GitHub commits. Click on a build number, then look at the build cause display area (typically near the build summary). Inspect the rendered HTML for the GitHub username field to see if it contains raw, unescaped characters
    Affected if The build cause display shows GitHub username data without proper HTML encoding (visible <script> tags, unescaped quotes, or raw special characters in the username field)

You are affected if DotCi plugin version is 2.40.00 or earlier AND GitHub commit notifications are being processed and displayed in the build cause area.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.40.00
Interim mitigation

Update the DotCi Plugin to version 2.40.01 or later which implements proper output encoding for the GitHub username field, or apply input validation on commit notification parameters before display.

Recommended fix High confidence

DotCi plugin version 2.40.01

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Locate the DotCi plugin in the list
  4. 4. If an update is available, click 'Update' to upgrade to the fixed version
  5. 5. After update completes, restart Jenkins if required
  6. 6. Verify the plugin is running at version 2.40.01 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dotci Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41239 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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