# CVE-2019-1003044: Jenkins Slack Notification Plugin CSRF vulnerability and missing permission checks

> Attackers can exploit CSRF to connect to malicious URLs using stolen credentials, capturing sensitive data stored in Jenkins.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5r8q-9fwv-2gpr

## What is CVE-2019-1003044?

CVE-2019-1003044 is a high-severity vulnerability in Jenkins Slack Notification Plugin, published on 28 Mar 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-1003044?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:slack. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:slack` | Maven | All versions | 2.20 |
| `org.jenkins-ci.plugins:slack` | Maven | All versions | 2.20 |

Products: Jenkins Slack Notification.

## How do I fix CVE-2019-1003044?

Upgrade org.jenkins-ci.plugins:slack to 2.20 or later.

## Is CVE-2019-1003044 being exploited?

There is no known exploitation of CVE-2019-1003044 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Slack Notification Plugin

- [CVE-2019-1003043](https://insights.sbomify.com/CVE-2019-1003043/): Jenkins Slack Notification Plugin missing permission check (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1003044 and fix it if it is affected.

What it is: CVE-2019-1003044 is a high-severity vulnerability in Jenkins Slack Notification Plugin, published on 28 Mar 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1003044 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:slack (Maven): affected all versions; fixed in 2.20
- org.jenkins-ci.plugins:slack (Maven): affected all versions; fixed in 2.20

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1003044/ (Markdown: https://insights.sbomify.com/CVE-2019-1003044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1003044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1003044
- OSV: https://osv.dev/vulnerability/CVE-2019-1003044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1003044/
Summaries are generated and may contain mistakes; the official description above is the record.