CVE-2024-23900 is a medium-severity (CVSS 4.3) vulnerability in org.jenkins-ci.plugins:matrix-project. A fix is available for org.jenkins-ci.plugins:matrix-project — see the affected versions and patch details below.
Path traversal vulnerability in Jenkins Matrix Project Plugin
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-23900.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:matrix-projectReal-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 Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects submitted through the config.xml REST API endpoint.
This allows attackers with Item/Configure permission to create or replace any config.xml file on the Jenkins controller file system with content not controllable by the attackers.
Matrix Project Plugin 822.824.v14451b_c0fd42 sanitizes user-defined axis names of Multi-configuration project.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:matrix-project | all versions | 822.824.v14451borg.jenkins-ci.plugins:matrix-project:822.824.v14451b |
Affected Products
matrix projectjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:matrix-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:matrix-project to 822.824.v14451b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23900 is resolved across your whole dependency graph.
Workarounds
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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.440.3.1716445200-3.el8 | RHSA-2024:3635 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.440.3.1716445150-3.el8 | RHSA-2024:3636 |
| OCP-Tools-4.14-RHEL-8 | jenkins-0:2.440.3.1716387933-3.el8 | RHSA-2024:3634 |
| OCP-Tools-4.15-RHEL-8 | jenkins-0:2.440.3.1718879390-3.el8 | RHSA-2024:4597 |
Frequently Asked Questions
Is CVE-2024-23900 in your dependencies?
Find it across Maven, including transitive dependencies.