dbcve.org
Blue OceanApplication · Jenkins

CVE-2019-1003013

MEDIUM · 5.4 CVSS v3.0 Published 2019-02-06
Fix available
A fix is available. Upgrade to after 1.10.1 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
An cross-site scripting vulnerability exists in Jenkins Blue Ocean Plugins 1.10.1 and earlier in blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/Export.java, blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/export/ExportConfig.java, blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/export/JSONDataWriter.java, blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/UserStatePreloader.java, blueocean-web/src/main/resources/io/jenkins/blueocean/PageStatePreloadDecorator/header.jelly that allows attackers with permission to edit a user's description in Jenkins to have Blue Ocean render arbitrary HTML when using it as that user.

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

A stored cross-site scripting (XSS) vulnerability in Jenkins Blue Ocean Plugins 1.10.1 and earlier allows attackers with permission to edit a user's description to inject arbitrary HTML/JavaScript that gets rendered when other users view that user in Blue Ocean, due to improper handling of user description in multiple files including Export.java, ExportConfig.java, JSONDataWriter.java, UserStatePreloader.java, and header.jelly.

MitigationUpgrade Blue Ocean plugin to version 1.10.2 or later which includes proper output encoding/sanitization of user descriptions to prevent XSS attacks.

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
Blue OceanApplication
Affected:<= 1.10.1
Openshift Container PlatformApplication
Affected:= 3.11

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

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

  1. Check Blue Ocean plugin version in Jenkins
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i blueocean
    Affected if Blue Ocean plugin version is 1.10.1 or earlier
  2. Check Jenkins version as fallback
    If unable to verify Blue Ocean directly, check Jenkins core version at Manage Jenkins > About Jenkins, then cross-reference with Blue Ocean bundle version for your Jenkins release
    Affected if Jenkins version bundles Blue Ocean 1.10.1 or earlier
  3. Verify OpenShift Container Platform version
    For OpenShift environments, check OCP version: oc get clusterversion -o jsonpath='{.items[0].status.desired.version}' or check the OCP release notes
    Affected if Running OpenShift Container Platform exactly version 3.11 (includes vulnerable Blue Ocean)
  4. Inspect user descriptions for existing XSS payloads
    Use Jenkins API or UI to review user descriptions: /api/json?tree=users[description] or view user profiles in Blue Ocean interface
    Affected if Any user description contains unencoded HTML/JavaScript tags (<script>, <img onerror=, javascript:, etc.)

You are affected if Blue Ocean plugin is version 1.10.1 or earlier, or if running OCP 3.11 with Blue Ocean installed, and users have permission to edit descriptions in Blue Ocean.

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.

From vendor data
Upgrade available Upgrade to a release after 1.10.1
Interim mitigation

Upgrade Blue Ocean plugin to version 1.10.2 or later which includes proper output encoding/sanitization of user descriptions to prevent XSS attacks.

Fix this in Blue Ocean Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003013 — 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-2019-1003013 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