JenkinsApplication
CVE-2017-2607
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 before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users, or users with SCM access, could configure jobs or modify build scripts such that they print serialized console notes that perform cross-site scripting attacks on Jenkins users viewing the build logs.
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 confidenceA persisted cross-site scripting (XSS) vulnerability in Jenkins console notes allows malicious users with job or SCM access to inject serialized console notes into build logs. When other users view these logs, the XSS payload executes in their browser. The vulnerability exists in Jenkins before versions 2.44 and 2.32.2.
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.44< 2.32.2CVSS 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.0/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 installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or append /about/ to your Jenkins URL. Alternatively, check the version file on the server (jenkins.war version or package manager listing).Affected if The installed version is less than 2.44 or less than 2.32.2 LTS.
-
Identify users with job or SCM accessReview Jenkins authorization matrix or role-based access control settings under Manage Jenkins > Configure Global Security. List all users or groups granted Job/Configure or SCM permissions.Affected if Any untrusted or compromised user accounts have job creation or SCM configuration permissions.
-
Inspect recent build logs for suspicious console notesReview build logs (console output) from recent builds, particularly those triggered by users with elevated permissions. Look for unusual sequences or patterns that may indicate injected console notes.Affected if Console output contains unexpected ANSI color codes, timestamps, or text patterns that were not produced by your build scripts.
-
Audit job configurations for unauthorized changesExamine job configurations under each job's Configure page. Look for unexpected build steps, pre-build scripts, or SCM polling configurations that could inject malicious console notes.Affected if Job configurations contain unfamiliar build steps, scripts, or SCM settings not authored by trusted administrators.
Your environment is affected if the Jenkins version is below 2.44 (or below 2.32.2 LTS) and untrusted users have job or SCM access that could inject console notes into build logs viewed by others.
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 data2.32.22.44
Upgrade Jenkins to version 2.44 or later (or 2.32.2 LTS or later) to remediate this vulnerability. Review job configurations and build scripts for any unauthorized console note injections.
Fix this in Jenkins
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2607 — 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-2017-2607 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