dbcve.org
Mattermost NotificationApplication · Jenkins

CVE-2019-10459

MEDIUM · 6.5 CVSS v3.1 Published 2019-10-23
Fix available
A fix is available. Upgrade to after 2.7.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Mattermost Notification Plugin 2.7.0 and earlier stored webhook URLs containing a secret token unencrypted in its global configuration file and job config.xml files on the Jenkins master where they could 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 Mattermost Notification Plugin versions 2.7.0 and earlier stored webhook URLs containing secret tokens in plaintext within global configuration files and job config.xml files. Users with Extended Read permission or filesystem access to the Jenkins master could view these unencrypted credentials.

MitigationUpgrade to a patched version of the plugin when available, or remove the plugin if unneeded. Rotate any exposed secret tokens immediately and restrict Extended Read permission to only authorized users.

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
Mattermost NotificationApplication
Affected:<= 2.7.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Mattermost Notification Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and look for Mattermost Notification Plugin in the list, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i mattermost
    Affected if plugin is present in the installed plugins list
  2. Check installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, find the Mattermost Notification Plugin and note the Version column, or inspect the plugin manifest file (META-INF/MANIFEST.MF) in the plugin directory
    Affected if version is 2.7.0 or earlier
  3. Inspect global configuration for plaintext credentials
    Navigate to the plugin's global configuration page (usually under Manage Jenkins > Configure System > Mattermost Notifications) and examine any configured webhook URLs. Also inspect the global configuration XML file in the Jenkins home directory for plaintext webhook URLs containing secret tokens
    Affected if webhook URLs in global config contain visible secret token strings in plaintext
  4. Inspect job configurations for plaintext credentials
    Review job config.xml files for each job that uses Mattermost notifications, looking for webhook URL fields that contain plaintext secret tokens. This can be done via the UI using Extended Read permission, or by examining the config.xml files directly in the job directories under $JENKINS_HOME/jobs/
    Affected if any job config.xml files contain plaintext webhook URLs with embedded secret tokens

User is affected if Mattermost Notification Plugin version 2.7.0 or earlier is installed AND plaintext webhook URLs with secret tokens are found in global or job configurations

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 2.7.0
Interim mitigation

Upgrade to a patched version of the plugin when available, or remove the plugin if unneeded. Rotate any exposed secret tokens immediately and restrict Extended Read permission to only authorized users.

Fix this in Mattermost Notification Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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