dbcve.org
Shelve ProjectApplication · Jenkins

CVE-2018-1999029

MEDIUM · 5.4 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to after 1.5 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
A cross-site scripting vulnerability exists in Jenkins Shelve Project Plugin 1.5 and earlier in ShelveProjectAction/index.jelly, ShelvedProjectsAction/index.jelly that allows attackers with Job/Configure permission to define JavaScript that would be executed in another user's browser when that other user performs some UI 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 confidence

Jenkins Shelve Project Plugin 1.5 and earlier contains a stored cross-site scripting (XSS) vulnerability in the ShelveProjectAction/index.jelly and ShelvedProjectsAction/index.jelly view files. Attackers with Job/Configure permission can inject malicious JavaScript that executes in other users' browsers when they interact with certain UI elements.

MitigationUpgrade Shelve Project Plugin to version 1.5.1 or later, which contains proper output encoding. Alternatively, restrict Job/Configure permission to trusted users only until the patch can be applied.

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
Shelve ProjectApplication
Affected:<= 1.5

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. Confirm Shelve Project Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'shelve-project' in the plugin list.
    Affected if The Shelve Project plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Shelve Project > click on the plugin to view version. Or check the file $JENKINS_HOME/plugins/shelve-project/META-INF/MANIFEST.MF for the Plugin-Version attribute.
    Affected if The version is 1.5 or any version earlier than 1.5
  3. Verify Job/Configure permission is granted broadly
    Navigate to Jenkins > Manage Jenkins > Configure Global Security > Authorization. Check if Job/Configure permission is given to users beyond administrators (for example, via Matrix Authorization Strategy or logged-in users can configure). Alternatively, review $JENKINS_HOME/config.xml or project-specific config.xml files for permission settings.
    Affected if Users other than trusted administrators have Job/Configure permission, enabling them to inject malicious script into shelved project metadata
  4. Confirm access to the vulnerable UI views
    Attempt to access the shelve project UI endpoints: navigate to a job > Shelve Project link, or check if the Shelved Projects link appears on the Jenkins main page. These views render the index.jelly files that contain the XSS vulnerability.
    Affected if The ShelveProjectAction or ShelvedProjectsAction views are accessible to users who can interact with shelved project entries

You are affected if the Shelve Project plugin is installed at version 1.5 or earlier AND users with Job/Configure permission can access the shelve project UI views.

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

Upgrade Shelve Project Plugin to version 1.5.1 or later, which contains proper output encoding. Alternatively, restrict Job/Configure permission to trusted users only until the patch can be applied.

Fix this in Shelve Project Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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