JenkinsApplication
CVE-2019-10402
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 · uneditedIn Jenkins 2.196 and earlier, LTS 2.176.3 and earlier, the f:combobox form control interpreted its item labels as HTML, resulting in a stored XSS vulnerability exploitable by users with permission to define its contents.
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 f:combobox form control in Jenkins 2.196 and earlier, LTS 2.176.3 and earlier did not properly sanitize item labels, interpreting them as raw HTML instead of escaping special characters. This allows authenticated users with permission to define combobox contents to inject malicious scripts that execute when other users view the affected form controls.
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.176.3<= 2.196CVSS 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.
-
Identify the installed Jenkins versionNavigate to Manage Jenkins > About Jenkins, or check the version via the URL /jenkins/admin or by reviewing the jenkins.war file properties. If using the CLI, run: java -jar jenkins-cli.jar -s http://[host]:[port] get-versionAffected if The version is 2.196 or earlier, or LTS 2.176.3 or earlier
-
Determine if f:combobox is used in your Jenkins configurationsSearch your Jenkins home directory for files containing the tag 'f:combobox' - look in .jelly or .groovy view files within your plugins or job configurations. Use a command like: grep -r 'f:combobox' $JENKINS_HOME/Affected if f:combobox tags are found in your view files or plugin configurations
-
Check permissions for users who can define form control contentsReview which users or groups have Overall/Administer permissions or permissions to configure jobs/views that contain f:combobox controls. Navigate to Manage Jenkins > Manage Users and check user permissions via Manage Jenkins > Manage Roles or matrix authorization settingsAffected if Users with only Overall/Read or limited permissions (but not Overall/Administer) can modify job configurations that contain f:combobox controls, meaning untrusted users can define combobox item labels
You are affected if your Jenkins version is 2.196 or earlier (or LTS 2.176.3 or earlier) AND you have f:combobox controls in use AND untrusted authenticated users can modify combobox item labels through job or view configurations.
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 dataUpgrade Jenkins to version 2.197 or LTS 2.176.4 or later, which properly escapes HTML in f:combobox item labels. Alternatively, restrict permissions for users who can define form control contents until patching is possible.
Fix this in Jenkins
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10402 — 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-2019-10402 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