# CVE-2022-36921: Missing permission check in Coverity Plugin allows capturing credentials

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

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** No
- **Published:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-99mq-hw5m-gwjj

## What is CVE-2022-36921?

CVE-2022-36921 is a high-severity missing authorization vulnerability in Jenkins Coverity Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins Coverity Plugin 1.11.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-862 (Missing Authorization)

## Which versions are affected by CVE-2022-36921?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:coverity` | Maven | All versions to 1.11.4 | None |
| `org.jenkins-ci.plugins:coverity` | Maven | All versions to 1.11.4 | None |

Products: Jenkins Coverity.

## How do I fix CVE-2022-36921?

No fix has been published for CVE-2022-36921 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-36921 being exploited?

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

## Other vulnerabilities in Jenkins Coverity Plugin

- [CVE-2022-36920](https://insights.sbomify.com/CVE-2022-36920/): Jenkins Coverity Plugin vulnerable to cross-site request forgery (CSRF) (high 8.8)
- [CVE-2018-1000104](https://insights.sbomify.com/CVE-2018-1000104/): Jenkins Coverity Plugin has Insufficiently Protected Credentials (high 7.8)
- [CVE-2022-36919](https://insights.sbomify.com/CVE-2022-36919/): Jenkins Coverity Plugin allows attackers with Overall/Read permission to enumerate credentials IDs (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36921 and fix it if it is affected.

What it is: CVE-2022-36921 is a high-severity missing authorization vulnerability in Jenkins Coverity Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36921 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:coverity (Maven): affected all versions up to 1.11.4; no fix listed
- org.jenkins-ci.plugins:coverity (Maven): affected all versions up to 1.11.4; no fix listed

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

## Sources

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

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