# CVE-2022-34798: Missing Authorization in Jenkins Deployment Dashboard Plugin

> Attackers with read permissions can access sensitive endpoints to connect to arbitrary URLs using stolen credentials due to missing permission checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 30 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q4mr-j6w9-r2mr

## What is CVE-2022-34798?

CVE-2022-34798 is a medium-severity missing authorization vulnerability in Jenkins Deployment Dashboard Plugin, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Deployment Dashboard Plugin 1.0.10 and earlier does not perform a permission check in several HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified HTTP URL using attacker-specified credentials.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:ec2-deployment-dashboard` | Maven | All versions to 1.0.10 | None |
| `org.jenkins-ci.plugins:ec2-deployment-dashboard` | Maven | All versions to 1.0.10 | None |

Products: Jenkins Deployment Dashboard.

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

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

## Is CVE-2022-34798 being exploited?

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

## Other vulnerabilities in Jenkins Deployment Dashboard Plugin

- [CVE-2022-34795](https://insights.sbomify.com/CVE-2022-34795/): Cross-site Scripting in Jenkins Deployment Dashboard Plugin (medium 5.4)
- [CVE-2023-50775](https://insights.sbomify.com/CVE-2023-50775/): Cross-site request forgery vulnerability in Jenkins Deployment Dashboard Plugin (medium 4.3)
- [CVE-2022-34796](https://insights.sbomify.com/CVE-2022-34796/): Jenkins Deployment Dashboard Plugin has Insufficiently Protected Credentials (medium 4.3)
- [CVE-2022-34797](https://insights.sbomify.com/CVE-2022-34797/): Cross-Site Request Forgery in Jenkins Deployment Dashboard Plugin (medium 4.3)
- [CVE-2022-34799](https://insights.sbomify.com/CVE-2022-34799/): Plaintext Storage of a Password in Jenkins Deployment Dashboard Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34798 is a medium-severity missing authorization vulnerability in Jenkins Deployment Dashboard Plugin, published on 30 Jun 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-34798 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:ec2-deployment-dashboard (Maven): affected all versions up to 1.0.10; no fix listed
- org.jenkins-ci.plugins:ec2-deployment-dashboard (Maven): affected all versions up to 1.0.10; 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-34798/ (Markdown: https://insights.sbomify.com/CVE-2022-34798/index.md)
```

## Sources

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

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