JenkinsApplication
CVE-2019-10403
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.196 and earlier, LTS 2.176.3 and earlier did not escape the SCM tag name on the tooltip for SCM tag actions, resulting in a stored XSS vulnerability exploitable by users able to control SCM tag names for these actions.
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.196 and earlier, LTS 2.176.3 and earlier failed to properly escape SCM (Source Code Management) tag names when rendering them in tooltips for SCM tag actions. This allowed attackers with the ability to control SCM tag names to inject malicious JavaScript code that would execute in the browsers of users viewing these tooltips—a stored XSS vulnerability.
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.
-
Check your Jenkins versionLog into the Jenkins web UI and navigate to 'Manage Jenkins' > 'About Jenkins', or use the command 'java -jar jenkins.war --version' for standalone installations, or query the /api/json endpointAffected if The version is 2.196 or earlier, or LTS 2.176.3 or earlier
-
Determine if SCM repository tagging is in useReview your Jenkins jobs and pipelines to see if they use Git, Subversion, or other version control systems with tagging features enabled. Check job configurations under 'Source Code Management' sectionsAffected if Jobs are configured with SCM repositories that support tagging functionality (such as Git with the 'Tag' action or Subversion with tags)
-
Identify users with SCM tag creation or modification permissionsNavigate to 'Manage Jenkins' > 'Manage Users' and review which users or groups have permissions to create or modify SCM-related configurations. Also check if anonymous users have extended read permissionsAffected if Users other than administrators have the ability to create, push, or modify SCM tags in repository configurations or pipeline scripts
-
Verify tooltip rendering in SCM tag actionsIf you have a job with SCM repository configuration, go to the job page, locate any SCM tag-related actions in the sidebar, and hover over the tag names in tooltips to inspect if they render as plain text without proper HTML escapingAffected if SCM tag names render with potential HTML or JavaScript characters visible in the tooltip (indicating lack of escaping)
You are affected if your Jenkins version is 2.196 or earlier (or LTS 2.176.3 or earlier) AND you have SCM repositories with tagging enabled where non-admin users can control tag names that get rendered in the Jenkins UI.
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 Jenkins to version 2.197 or later, or LTS 2.176.4 or later, which includes proper HTML escaping of SCM tag names in tooltips. Until patched, limit which users can create or modify SCM tag names.
Fix this in Jenkins
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10403 — 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-10403 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