# CVE-2022-25204: Protection Mechanism Failure in Jenkins Doktor Plugin

> Attackers controlling agent processes can determine if specific files exist on the Jenkins controller via error messages in the Doktor Plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 15 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-64q9-f38h-9mwx

## What is CVE-2022-25204?

CVE-2022-25204 is a medium-severity vulnerability in Jenkins Doktor Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Doktor Plugin 0.4.1 and earlier implements functionality that allows agent processes to render files on the controller as Markdown or Asciidoc, and error messages allow attackers able to control agent processes to determine whether a file with a given name exists.

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

2 open source packages ship an affected version, including by.dev.madhead.doktor:doktor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `by.dev.madhead.doktor:doktor` | Maven | All versions to 0.4.1 | None |
| `by.dev.madhead.doktor:doktor` | Maven | All versions to 0.4.1 | None |

Products: Jenkins Doktor.

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

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

## Is CVE-2022-25204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25204 is a medium-severity vulnerability in Jenkins Doktor Plugin, published on 15 Feb 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-25204 in the wild and no public exploit code.

Affected packages and fixed versions:
- by.dev.madhead.doktor:doktor (Maven): affected all versions up to 0.4.1; no fix listed
- by.dev.madhead.doktor:doktor (Maven): affected all versions up to 0.4.1; 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-25204/ (Markdown: https://insights.sbomify.com/CVE-2022-25204/index.md)
```

## Sources

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

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