dbcve.org
Jira Issue UpdaterApplication · Jenkins

CVE-2019-1003054

HIGH · 8.8 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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 Issue Updater Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.

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 Issue Updater Plugin stores Jira API tokens and credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission (a permission designed for safe viewing of job configurations) can view these credentials, as can anyone with filesystem access to the Jenkins master.

MitigationUpgrade the Jira Issue Updater Plugin to a version that encrypts credentials, or migrate to Jenkins' built-in credential storage mechanism (Credentials Plugin). All exposed credentials should be rotated immediately after remediation.

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
Jira Issue UpdaterApplication
Affected:all versions

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check if Jira Issue Updater plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: jenkins-cli.jar or REST API /pluginManager/plugin/{pluginName}/api/json to list installed plugins. Look for 'Jira Issue Updater' in the list.
    Affected if The plugin appears in the installed plugins list. Since all versions are affected, any version confirms exposure risk.
  2. Identify jobs using Jira Issue Updater
    Search job config.xml files for the presence of the 'jira' or 'jiraissueupdater' element or builder type. This can be done via: find $JENKINS_HOME/jobs -name 'config.xml' -exec grep -l -i 'jira' {} \; or using the Jenkins REST API to query job configurations.
    Affected if Any job config.xml contains Jira-related configuration elements, indicating the plugin is in use.
  3. Inspect job config.xml for plaintext credentials
    Examine the config.xml files of jobs using the plugin. Look for plaintext API tokens, passwords, or credentials stored within Jira-related XML elements. Open a sample config.xml in a text editor or use: cat $JENKINS_HOME/jobs/JOBNAME/config.xml | grep -i 'token\|password\|secret'
    Affected if The config.xml contains visible plaintext strings matching Jira API token patterns (typically alphanumeric strings of 24-32 characters) or clearly labeled password/token fields within Jira builder sections.
  4. Verify Extended Read permission is granted
    Navigate to Manage Jenkins > Manage Users > security realm > matrix-based security, or check $JENKINS_HOME/users/*/config.xml for authorization matrix entries. Look for the 'ExtendedRead' permission assigned to any user or group.
    Affected if Any user or group has ExtendedRead permission enabled in the Jenkins authorization matrix, allowing them to read job configurations.
  5. Check filesystem access to Jenkins home directory
    Review file system permissions on $JENKINS_HOME/jobs/*/config.xml. Run: ls -la $JENKINS_HOME/jobs/ */config.xml to see who has read access beyond the Jenkins service account.
    Affected if Non-admin system users or processes have read access to the Jenkins home directory where job configurations are stored.

If the Jira Issue Updater plugin is installed and any job config.xml contains plaintext Jira API tokens or credentials, combined with users having ExtendedRead permission or shared filesystem access, the environment is vulnerable and credentials have been exposed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Jira Issue Updater Plugin to a version that encrypts credentials, or migrate to Jenkins' built-in credential storage mechanism (Credentials Plugin). All exposed credentials should be rotated immediately after remediation.

Fix this in Jira Issue Updater Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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