Agent-to-controller filename disclosure via rendering errors
Published Feb 15, 2022 · Updated Aug 3, 2024
Agent-to-controller security bypass in Jenkins Doktor Plugin 0.4.1 and earlier allows attackers to test controller file existence. The plugin lets an agent process submit a controller-side file path for Markdown or Asciidoc rendering and exposes path-dependent errors. Control of a connected Jenkins agent process is required, and the resulting oracle reveals only whether a chosen filename exists.
Summary
What happened
Agent-to-controller security bypass in Jenkins Doktor Plugin 0.4.1 and earlier allows attackers to test controller file existence. The plugin lets an agent process submit a controller-side file path for Markdown or Asciidoc rendering and exposes path-dependent errors. Control of a connected Jenkins agent process is required, and the resulting oracle reveals only whether a chosen filename exists.
The record
- CVE
- CVE-2022-25204
- Published
- Feb 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Doktor
- Classifications
- T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=0.4.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo