dbcve.org
IrcApplication · Jenkins

CVE-2019-1003051

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 IRC Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with 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 IRC Plugin stores IRC connection credentials (such as passwords or API tokens) in plaintext within its global configuration XML file on the Jenkins master filesystem. Any user with read access to the Jenkins home directory can retrieve these credentials directly from the configuration file without authentication.

MitigationMigrate credentials to Jenkins' built-in Credentials Store using the plugin's support for secure credential storage, or upgrade the plugin to a version that implements encryption. Revoke and rotate any exposed credentials immediately.

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
IrcApplication
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. Confirm Jenkins IRC Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and look for 'IRC Plugin' or 'IRC Bot' in the list, or check for ircbot or irc plugin directories in $JENKINS_HOME/plugins/
    Affected if The IRC Plugin appears in the installed plugins list
  2. Locate the IRC plugin global configuration file
    In the Jenkins home directory, look for an XML file containing IRC plugin configuration. Common locations include $JENKINS_HOME/org.jenkinsci.plugins.ircbot.GlobalPluginConfiguration.xml or a config.xml file within an ircbot plugin directory
    Affected if A configuration XML file for the IRC plugin exists in the Jenkins home directory
  3. Examine the configuration file for plaintext credentials
    Open the IRC plugin configuration XML file and search for elements containing 'password', 'pass', 'token', 'credentials', or 'secret'. Look for plain text values inside these tags rather than masked or encrypted strings
    Affected if The configuration file contains plaintext password, token, or API credential values in clear text (not masked, not encrypted, not referencing Jenkins credential IDs)
  4. Verify credentials are not using Jenkins credential binding
    Review the same configuration file to determine if credential values are stored as direct plaintext strings or if they reference credential IDs from Jenkins' built-in credentials store (typically identified by <credentialsId> or similar tags)
    Affected if Credentials are stored as direct string values rather than credential ID references

If the IRC Plugin is installed AND its global configuration XML file contains plaintext password or token values (not masked, not encrypted, and not using Jenkins credential ID references), the environment is affected by this vulnerability.

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

Migrate credentials to Jenkins' built-in Credentials Store using the plugin's support for secure credential storage, or upgrade the plugin to a version that implements encryption. Revoke and rotate any exposed credentials immediately.

Fix this in Irc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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