# CVE-2022-34809: Password stored in plain text by Jenkins RQM Plugin

> Attackers with file system access can read unencrypted passwords from the Jenkins RQM Plugin configuration file.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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-m59q-vgq9-75cr

## What is CVE-2022-34809?

CVE-2022-34809 is a medium-severity vulnerability in Jenkins RQM 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 RQM Plugin 2.8 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

2 open source packages ship an affected version, including net.praqma:rqm-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.praqma:rqm-plugin` | Maven | All versions to 2.8 | None |
| `net.praqma:rqm-plugin` | Maven | All versions to 2.8 | None |

Products: Jenkins Rqm.

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

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

## Is CVE-2022-34809 being exploited?

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

## Other vulnerabilities in Jenkins RQM Plugin

- [CVE-2022-41241](https://insights.sbomify.com/CVE-2022-41241/): Jenkins RQM Plugin vulnerable to Improper Restriction of XML External Entity Reference (critical 9.8)
- [CVE-2022-34810](https://insights.sbomify.com/CVE-2022-34810/): Jenkins RQM Plugin allows enumerating credentials IDs due to missing permission check (medium 6.5)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- net.praqma:rqm-plugin (Maven): affected all versions up to 2.8; no fix listed
- net.praqma:rqm-plugin (Maven): affected all versions up to 2.8; 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-34809/ (Markdown: https://insights.sbomify.com/CVE-2022-34809/index.md)
```

## Sources

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

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