Configuration overwrite via unsanitized matrix axis names
Published Jan 24, 2024 · Updated Jun 16, 2025
Path traversal in Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier allows remote authenticated users to replace config.xml files. The config.xml REST endpoint accepts user-defined matrix axis names without sanitization, allowing those names to escape the intended project path. Item/Configure permission is required; attackers can create or replace controller config.xml files but cannot control the written content.
Summary
What happened
Path traversal in Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier allows remote authenticated users to replace config.xml files. The config.xml REST endpoint accepts user-defined matrix axis names without sanitization, allowing those names to escape the intended project path. Item/Configure permission is required; attackers can create or replace controller config.xml files but cannot control the written content.
The record
- CVE
- CVE-2024-23900
- Published
- Jan 24, 2024
- Updated
- Jun 16, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Matrix Project Plugin
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- Jun 16, 2025Record 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=0 <=822.v01b_8c85d16d2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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