dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Oct 2025.
JenkinsApplication

CVE-2017-1000353

CRITICAL · 9.8 CVSS v3.1 Published 2018-01-29
Fix available
A fix is available. Upgrade to after 2.56 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java `SignedObject` object to the Jenkins CLI, that would be deserialized using a new `ObjectInputStream`, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding `SignedObject` to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default.

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 confidence

Jenkins versions 2.56 and earlier and LTS 2.46.1 and earlier contain an unauthenticated remote code execution vulnerability. Attackers exploit Java deserialization by sending a maliciously crafted SignedObject to the Jenkins CLI, which gets deserialized using a new ObjectInputStream that bypasses the blacklist-based protection mechanism, enabling full RCE without authentication.

MitigationUpgrade to Jenkins 2.57+ or LTS 2.46.2+ to receive the blacklist update that includes SignedObject, and disable the remoting-based CLI protocol to prevent deserialization attacks.

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
Affected:<= 2.56<= 2.46.1
Communications Cloud Native Core Automated Test SuiteApplication
Affected:= 1.9.0

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jenkins version
    Access the Jenkins web UI and navigate to 'Manage Jenkins' > 'System Information' or check the version displayed on the login page. Alternatively, run 'java -jar jenkins.war --version' from the Jenkins WAR file location.
    Affected if The installed version is 2.56 or earlier, or 2.46.1 LTS or earlier
  2. Confirm CLI is enabled
    Navigate to 'Manage Jenkins' > 'Configure Global Security' and locate the 'CLI' section. Check if any CLI transport mechanisms are enabled, particularly the Remoting-based protocol which handles the vulnerable ObjectInputStream.
    Affected if CLI is enabled and accessible over remoting/JAR transport (port typically 33848 or 50000)
  3. Verify deserialization blacklist
    Check the Jenkins configuration file (typically $JENKINS_HOME/init.groovy.d/ or the system configuration) for the 'hudson.remoting.Engine' or blacklist settings. The blacklist should include 'javx.securitySignedObject' if patched.
    Affected if The blacklist does NOT contain SignedObject, indicating the mitigation is not applied

A user is affected if their Jenkins version is 2.56 or earlier (or 2.46.1 LTS or earlier) AND the CLI remoting protocol is enabled, with SignedObject absent from the deserialization blacklist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.56
Vendor patch www.oracle.com →
Interim mitigation

Upgrade to Jenkins 2.57+ or LTS 2.46.2+ to receive the blacklist update that includes SignedObject, and disable the remoting-based CLI protocol to prevent deserialization attacks.

Recommended fix High confidence

Jenkins 2.57 (weekly) or Jenkins LTS 2.46.2

  1. 1. Back up your current Jenkins configuration and data
  2. 2. Download Jenkins 2.57 (weekly release) or Jenkins LTS 2.46.2 from jenkins.io/download
  3. 3. If running Jenkins via WAR file, replace the existing jenkins.war with the new version
  4. 4. If using a package manager (apt, yum, brew), update the package to version 2.57 or 2.46.2
  5. 5. Restart Jenkins service to apply the update
  6. 6. Verify the upgrade by logging into the Jenkins dashboard
  7. 7. Confirm SignedObject is now blacklisted by checking the security configuration
Caveat The remoting-based CLI protocol is disabled by default after upgrade; ensure any CLI clients use the new HTTP protocol

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000353 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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