JenkinsApplication
CVE-2024-23898
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins versions 2.217-2.441 and LTS 2.222.1-2.426.2 fail to validate the origin header on CLI WebSocket connections, enabling cross-site WebSocket hijacking (CSWSH). An attacker can trick a authenticated user's browser into establishing a WebSocket connection to the Jenkins controller, allowing arbitrary CLI command execution with the victim's privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
>= 2.217, <= 2.441>= 2.222.1, <= 2.426.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Jenkins versionNavigate to Manage Jenkins > About Jenkins, or access /api/json?tree=version from the Jenkins root URLAffected if The version falls within 2.217-2.441 or LTS 2.222.1-2.426.2, meaning it is affected and needs upgrading to 2.442+ or LTS 2.426.3+
-
Verify CLI over WebSocket is enabledNavigate to Manage Jenkins > CLI or inspect the Jenkins configuration files for CLI-related settings. Check if the 'Java Web Start' or 'CLI' Remoting mode is active, as WebSocket connections are used for CLI communication.Affected if CLI access is enabled and accessible via WebSocket, which is required for the CSWSH attack to succeed
-
Confirm Jenkins is network-accessible from untrusted browsersDetermine if the Jenkins UI is exposed to the internet or accessible from browsers on untrusted networks, as the CSWSH attack requires a victim's browser to initiate the WebSocket connectionAffected if Jenkins is reachable from web browsers outside a trusted network, enabling an attacker to trick authenticated users into establishing malicious WebSocket connections
You are affected if your Jenkins version is between 2.217-2.441 or LTS 2.222.1-2.426.2 AND CLI WebSocket connections are enabled AND the instance is accessible from browsers that an attacker could target.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Jenkins to version 2.442+ or LTS 2.426.3+. As a workaround, disable CLI access or restrict WebSocket connections at the network level.
Jenkins 2.442 or Jenkins LTS 2.426.3
- 1. Backup your Jenkins configuration and plugins before upgrading
- 2. Download Jenkins 2.442 (or the latest available version) from jenkins.io, or download Jenkins LTS 2.426.3
- 3. If running Jenkins via WAR file, replace the existing jenkins.war with the new version
- 4. If using a package manager (apt, yum, brew, Docker), update to the new version
- 5. Restart Jenkins service to apply the update
- 6. Verify the upgrade by checking the Jenkins version in the UI (Manage Jenkins > About Jenkins)
- 7. Test CLI commands to ensure functionality is restored after the origin validation fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23898 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23898 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data