dbcve.org
JiraApplication · Jenkins

CVE-2019-16541

CRITICAL · 9.9 CVSS v3.1 Published 2019-11-21
Fix available
A fix is available. Upgrade to after 3.0.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Jenkins JIRA Plugin 3.0.10 and earlier does not declare the correct (folder) scope for per-folder Jira site definitions, allowing users to select and use credentials with System scope.

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 JIRA Plugin versions 3.0.10 and earlier fails to properly declare a folder scope for per-folder Jira site definitions. This misconfiguration allows users with folder-level access to select and use credentials that were intended for System scope (global credentials), enabling potential privilege escalation across folders.

MitigationUpdate Jenkins JIRA Plugin to version 3.0.11 or later which properly declares folder scope. Review all folder-level Jira site definitions and ensure credentials are correctly scoped (folder-specific rather than system-wide).

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
JiraApplication
Affected:<= 3.0.10

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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. Identify JIRA Plugin installation
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'JIRA' or check the plugin directory $JENKINS_HOME/plugins for the jira folder
    Affected if The JIRA plugin is not installed or the jira folder does not exist in the plugins directory
  2. Check JIRA Plugin version
    In Manage Jenkins > Manage Plugins > Installed, locate the JIRA Plugin and note the version number under the Version column
    Affected if The installed version is 3.0.10 or earlier
  3. Verify folder-level Jira site definitions exist
    Navigate to a specific folder > Configure and look for Jira Sites configuration section, or inspect folder config.xml files in $JENKINS_HOME/jobs/<folder>/config.xml for <jiraSite> elements
    Affected if Any folder contains Jira site definitions configured (jiraSite elements present in folder configs)
  4. Inspect credential scope in folder Jira configurations
    In folder Configure > Jira Sites, examine which credentials are selected for each folder-level site; compare against Manage Credentials to determine if System-scoped (global) credentials are being used in folder contexts
    Affected if Folder-level Jira site definitions are using credentials marked as System scope (global) rather than folder-specific credentials

You are affected if the JIRA Plugin version is 3.0.10 or earlier AND folder-level Jira site definitions exist that use System-scoped (global) credentials.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.0.10
Interim mitigation

Update Jenkins JIRA Plugin to version 3.0.11 or later which properly declares folder scope. Review all folder-level Jira site definitions and ensure credentials are correctly scoped (folder-specific rather than system-wide).

Recommended fix Moderate confidence

JIRA Plugin 3.0.11 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the "Installed" tab
  3. 3. Search for "JIRA" in the plugin list
  4. 4. If JIRA Plugin version 3.0.10 or earlier is installed, locate the update available version in the "Updates" tab
  5. 5. Select the JIRA Plugin and click "Update" to upgrade to the fixed version
  6. 6. After update completes, restart Jenkins or wait for plugin to reload

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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