dbcve.org
Slack NotificationApplication · Jenkins

CVE-2019-1003043

HIGH · 7.5 CVSS v3.1 Published 2019-03-28
Fix available
A fix is available. Upgrade to after 2.19 or later.
See remediation →
81/100
Remediation priority · High
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
A missing permission check in Jenkins Slack Notification Plugin 2.19 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

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 Slack Notification Plugin versions 2.19 and earlier lacks proper permission checks on configuration endpoints. Attackers with only Overall/Read permission (the lowest privilege level) can configure arbitrary URLs and specify credential IDs to exfiltrate stored Jenkins credentials, effectively bypassing the intended access controls.

MitigationUpgrade Jenkins Slack Notification Plugin to version 2.20 or later. As an interim measure, restrict user permissions to最小必要权限 and review credential storage configurations.

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
Slack NotificationApplication
Affected:<= 2.19

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify if Slack Notification Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (to confirm access) then check plugin listing
    Affected if The Slack Notification Plugin appears in the installed plugins list
  2. Check the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed > Slack Notification Plugin. Note the version number displayed
    Affected if The version is 2.19 or lower (e.g., 2.19, 2.18, 2.17, etc.)
  3. Verify configuration endpoint access for low-privilege users
    Create or use a test user account with only Overall/Read permission. Attempt to access the Slack notification configuration page at: /jenkins/slack/notify or /jenkins/job/.../configure (where Slack notifications are configured)
    Affected if A user with only Overall/Read permission can view or modify Slack notification settings without receiving an authentication/authorization error
  4. Check for configured credentials in Slack notification settings
    As an admin, review the Slack notification configuration at: Manage Jenkins > Configure System > Slack or within job configurations. Look for any saved credentials or credential IDs
    Affected if Slack notifications are configured with stored Jenkins credentials (e.g., API tokens, bot tokens)
  5. Review audit logs for unauthorized Slack configuration changes
    Check Jenkins logs or audit logs for access to Slack configuration endpoints from low-privilege user accounts
    Affected if Logs show low-privilege users accessing or modifying Slack notification configuration endpoints

Your environment is affected if the Jenkins Slack Notification Plugin version is 2.19 or earlier AND users with only Overall/Read permission can access or modify Slack notification configuration settings that contain stored 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.

From vendor data
Upgrade available Upgrade to a release after 2.19
Interim mitigation

Upgrade Jenkins Slack Notification Plugin to version 2.20 or later. As an interim measure, restrict user permissions to最小必要权限 and review credential storage configurations.

Fix this in Slack Notification Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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