CVE-2024-23898: Jenkins 2.217 through 2.441 (both inclusive), LTS 2.222.1 through 2.426.2 (both inclusive) does not perform origin validation of requests ma
Noroxi assessment
Priority: Plan (action score 55/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 67.1% (FIRST EPSS); higher than 99.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.jenkins-ci.main:jenkins-core (Maven) 2.426.3, 2.442; jenkins (Red Hat:ocp_tools:4.11::el8) 0:2.426.3.1706516929-3.el8; jenkins-2-plugins (Red Hat:ocp_tools:4.11::el8) 0:4.11.1706516946-1.el8.
Add it to your regular patch cycle. Upgrade to org.jenkins-ci.main:jenkins-core (Maven) 2.426.3, 2.442; jenkins (Red Hat:ocp_tools:4.11::el8) 0:2.426.3.1706516929-3.el8; jenkins-2-plugins (Red Hat:ocp_tools:4.11::el8) 0:4.11.1706516946-1.el8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Jenkins 2.217 through 2.441 (both inclusive), LTS 2.222.1 through 2.426.2 (both inclusive) does not perform origin validation of requests made through the CLI WebSocket endpoint, resulting in a cross-site WebSocket hijacking (CSWSH) vulnerability, allowing attackers to execute CLI commands on the Jenkins controller.
- Published
- Jan 24, 2024
- Updated
- Jun 17, 2026
- EPSS
- 67.1% · 99th percentile
- CWE
- CWE-346
Report tools
Action score
55
Plan
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 20 / 30 · 67.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jenkins | jenkins | cpe:2.3:a:jenkins:jenkins |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins jenkins2.217 and later · up to 2.441 inclusive
- jenkins jenkins2.222.1 and later · up to 2.426.2 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.
Jenkins Project Jenkins
- before 2.217not affected · maven
- 2.442 and laternot affected · maven
- 2.426.3 and later · before 2.426.*not affected · maven
- 2.440.1 and later · before 2.440.*not affected · maven
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.jenkins-ci.main:jenkins-core | from 2.217 · before 2.426.3 | 2.426.3 |
| Maven | org.jenkins-ci.main:jenkins-core | from 2.427 · before 2.442 | 2.442 |
| Maven | org.jenkins-ci.main:jenkins-core | from 2.441 · up to and including 2.441 | — |
| Red Hat:ocp_tools:4.11::el8 | jenkins | before 0:2.426.3.1706516929-3.el8 | 0:2.426.3.1706516929-3.el8 |
| Red Hat:ocp_tools:4.11::el8 | jenkins-2-plugins | before 0:4.11.1706516946-1.el8 | 0:4.11.1706516946-1.el8 |
| Red Hat:ocp_tools:4.13::el8 | jenkins | before 0:2.426.3.1706516254-3.el8 | 0:2.426.3.1706516254-3.el8 |
| Red Hat:ocp_tools:4.13::el8 | jenkins-2-plugins | before 0:4.13.1706516346-1.el8 | 0:4.13.1706516346-1.el8 |
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-23897Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character folloKEV99Now
- CVE-2017-1000353Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution.KEV99Now
- CVE-2018-1000861A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/corKEV98Now
Published before and after this one in the same product
- ← EarlierCVE-2023-43497Sep 20, 2023 · In Jenkins 2.423 and earlier, LTS 2.414.1 and earlier, processing file uploads using the Stapler web framework creates temporary files in th32Monitor
- ← EarlierCVE-2023-43498Sep 20, 2023 · In Jenkins 2.423 and earlier, LTS 2.414.1 and earlier, processing file uploads using MultipartFormDataParser creates temporary files in the 32Monitor
- Later →CVE-2024-43044Aug 7, 2024 · Jenkins 2.470 and earlier, LTS 2.452.3 and earlier allows agent processes to read arbitrary files from the Jenkins controller file system by44Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.jenkins-ci.main:jenkins-core | 2.426.3 | Package registry (OSV) |
| Maven:org.jenkins-ci.main:jenkins-core | 2.442 | Package registry (OSV) |
| red hat:jenkins | 0:2.426.3.1706516929-3.el8 · Red Hat:ocp_tools:4.11::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.11.1706516946-1.el8 · Red Hat:ocp_tools:4.11::el8 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:2 | 2024-11-14 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+294 d
- TodayNov 8, 2026+1019 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-346 · Origin Validation ErrorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Exploit Script-Based APIsCAPEC-160Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-Middle: ARP Cache PoisoningT1557.002
- Compromise Infrastructure: DNS ServerT1584.002
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.