# CVE-2020-2117: Missing permission checks in Pipeline GitHub Notify Step Plugin allows capturing credentials

> Attackers with read access can exploit missing permission checks to capture stored Jenkins credentials by connecting to attacker-controlled URLs.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x7rc-5mjg-5pvr

## What is CVE-2020-2117?

CVE-2020-2117 is a medium-severity missing authorization vulnerability in Jenkins Pipeline GitHub Notify Step Plugin, published on 12 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-2117?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-githubnotify-step` | Maven | All versions | 1.0.5 |
| `org.jenkins-ci.plugins:pipeline-githubnotify-step` | Maven | All versions | 1.0.5 |

Products: Jenkins Pipeline Github Notify Step.

## How do I fix CVE-2020-2117?

Upgrade org.jenkins-ci.plugins:pipeline-githubnotify-step to 1.0.5 or later.

## Is CVE-2020-2117 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline GitHub Notify Step Plugin

- [CVE-2020-2116](https://insights.sbomify.com/CVE-2020-2116/): CSRF vulnerability in Pipeline GitHub Notify Step Plugin allows capturing credentials (high 8.8)
- [CVE-2020-2118](https://insights.sbomify.com/CVE-2020-2118/): Users with Overall/Read access can enumerate credential IDs in Pipeline GitHub Notify Step Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2117 and fix it if it is affected.

What it is: CVE-2020-2117 is a medium-severity missing authorization vulnerability in Jenkins Pipeline GitHub Notify Step Plugin, published on 12 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2117 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-githubnotify-step (Maven): affected all versions; fixed in 1.0.5
- org.jenkins-ci.plugins:pipeline-githubnotify-step (Maven): affected all versions; fixed in 1.0.5

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-2020-2117/ (Markdown: https://insights.sbomify.com/CVE-2020-2117/index.md)
```

## Sources

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

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