How severe is CVE-2022-25204?

CVE-2022-25204 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-25204?

CVE-2022-25204 affects the following packages: by.dev.madhead.doktor:doktor (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-25204?

No patched version of by.dev.madhead.doktor:doktor has shipped for CVE-2022-25204 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2022-25204 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for by.dev.madhead.doktor:doktor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-25204 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-25204 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-25204 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-25204?

CVE-2022-25204 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-25204 published, and has it been updated?

CVE-2022-25204 was published on February 16, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-25204 — doktor

MEDIUM

CVE-2022-25204 is a medium-severity (CVSS 5.4) vulnerability in by.dev.madhead.doktor:doktor. No vendor fix is recorded yet; mitigation options are listed below.

Protection Mechanism Failure in Jenkins Doktor Plugin

Published

Feb 16, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-25204 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕by.dev.madhead.doktor:doktor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`by.dev.madhead.doktor:doktor`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

doktorjenkins

≤ 0.4.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for by.dev.madhead.doktor:doktor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of by.dev.madhead.doktor:doktor has shipped for CVE-2022-25204 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-25204 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works