# CVE-2022-34803: Jenkins OpsGenie Plugin Plaintext Storage of a Password vulnerability

> Attackers with Extended Read permission or file system access can view unencrypted OpsGenie API keys stored in Jenkins configuration files.

- **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:** No
- **Published:** 30 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-273c-fjw8-v2w8

## What is CVE-2022-34803?

CVE-2022-34803 is a medium-severity vulnerability in Jenkins OpsGenie 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 OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file and in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission (config.xml), or access to the Jenkins controller file system.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

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


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

Products: Jenkins Opsgenie.

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

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

## Is CVE-2022-34803 being exploited?

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

## Other vulnerabilities in Jenkins OpsGenie Plugin

- [CVE-2022-34804](https://insights.sbomify.com/CVE-2022-34804/): Jenkins OpsGenie Plugin vulnerable to Cleartext Transmission of Sensitive Information (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34803 is a medium-severity vulnerability in Jenkins OpsGenie 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-34803 in the wild and no public exploit code.

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

## Sources

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

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