dbcve.org
Global Build StatsApplication · Jenkins

CVE-2017-1000389

MEDIUM · 6.1 CVSS v3.0 Published 2018-01-26
Fix available
A fix is available. Upgrade to after 1.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Some URLs provided by Jenkins global-build-stats plugin version 1.4 and earlier returned a JSON response that contained request parameters. These responses had the Content Type: text/html, so could have been interpreted as HTML by clients, resulting in a potential reflected cross-site scripting vulnerability. Additionally, some URLs provided by global-build-stats plugin that modify data did not require POST requests to be sent, resulting in a potential cross-site request forgery 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 global-build-stats plugin versions 1.4 and earlier returns JSON data in responses with Content-Type: text/html, causing browsers to interpret the JSON as HTML and potentially execute malicious scripts (reflected XSS). Additionally, data-modifying endpoints lack POST request requirements, enabling cross-site request forgery attacks.

MitigationUpgrade the global-build-stats plugin to version 1.5 or later, which properly sets Content-Type headers to application/json and requires POST for state-changing requests. Until patched, consider disabling the plugin or implementing CSRF tokens in integrations.

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
Global Build StatsApplication
Affected:<= 1.4

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 global-build-stats plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'global-build-stats' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Determine the installed plugin version
    In the installed plugins list, locate the 'global-build-stats' plugin and note the version number displayed in the 'Version' column.
    Affected if The version number is 1.4 or earlier (e.g., 1.4, 1.3, 1.2, 1.1, 1.0).
  3. Identify plugin-managed URLs
    Access the plugin's API endpoints by reviewing the plugin documentation or accessing common paths such as /plugin/global-build-stats/api/ or /global-build-stats/ - these endpoints return JSON data about build statistics.
    Affected if The plugin is installed and accessible URLs exist that return JSON data.
  4. Check Content-Type header on JSON responses
    Use a browser developer tool or curl to request a JSON endpoint from the global-build-stats plugin (e.g., fetch a build-stats JSON API URL) and inspect the response headers. Look for the 'Content-Type' header in the HTTP response.
    Affected if The Content-Type header shows 'text/html' instead of 'application/json' when the endpoint returns JSON data.
  5. Test for CSRF vulnerability on state-changing endpoints
    Identify any endpoints that modify data (such as saving or clearing statistics) and attempt to trigger them using a GET request instead of POST, either via browser navigation or curl.
    Affected if State-changing operations complete successfully via GET request without requiring a POST method.

You are affected if the global-build-stats plugin is installed at version 1.4 or earlier and your JSON API responses return Content-Type: text/html or your data-modifying endpoints accept GET requests.

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.4
Interim mitigation

Upgrade the global-build-stats plugin to version 1.5 or later, which properly sets Content-Type headers to application/json and requires POST for state-changing requests. Until patched, consider disabling the plugin or implementing CSRF tokens in integrations.

Fix this in Global Build Stats Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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