Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:slack

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1MavenPublished

    Jenkins Slack Notification Plugin CSRF vulnerability and missing permission checks

    CVE-2019-1003044 · GHSA-5r8q-9fwv-2gpr

    Affected
    • Maven org.jenkins-ci.plugins:slack <= 2.19
    Fixed in
    2.20· Vendor fix available
    Issue
    A cross-site request forgery vulnerability in Jenkins Slack Notification Plugin 2.19 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

    Recommended action: Upgrade to 2.20 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.2MavenPublished

    Jenkins Slack Notification Plugin missing permission check

    CVE-2019-1003043 · GHSA-22xp-7rcx-xp34

    Affected
    • Maven org.jenkins-ci.plugins:slack <= 2.19
    Fixed in
    2.20· Vendor fix available
    Issue
    Jenkins Slack Notification Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. Additionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability. This form validation method now requires POST requests and Overall/Administer (for global configuration) or Item/Configure permissions (for job configuration).

    Recommended action: Upgrade to 2.20 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →