CVE-2017-1000353: Jenkins Remote Code Execution Vulnerability

Published Jan 29, 2018
·
Updated

Jenkins contains a remote code execution vulnerability. This vulnerability that could allowed attackers to transfer a serialized Java SignedObject object to the remoting-based Jenkins CLI, that would be deserialized using a new ObjectInputStream, bypassing the existing blocklist-based protection mechanism.

Other sources

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.

Affected Software

5 affected components
Jenkins Jenkins<=2.56
Jenkins Jenkins<=2.46.1
Oracle Communications Cloud Native Core Automated Test Suite=1.9.0
Jenkins Jenkins
Jenkins Jenkins<=2.56

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Jenkins to a version that resolves this vulnerability.

    Fixed in 2.46.2
  2. Configuration

    Disable the remoting-based (Java serialization) CLI protocol to prevent unauthenticated SignedObject instances from being deserialized.

    Jenkins CLI (remoting-based, Java serialization) CLI protocol (remoting-based) = disabled
  3. Configuration

    Add 'SignedObject' to the deserialization blacklist to block deserialization of java.security.SignedObject instances.

    Jenkins deserialization blacklist blacklist entry = SignedObject
  4. Compensating control

    Follow applicable BOD 22-01 guidance for cloud services.

  5. Compensating control

    Discontinue use of the product if mitigations are unavailable.

Event History

Jan 29, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 2, 2025
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-1000353?

CVE-2017-1000353 has been classified as a critical vulnerability due to its potential for unauthenticated remote code execution.

2

How do I fix CVE-2017-1000353?

To fix CVE-2017-1000353, update Jenkins to version 2.60 or later, or 2.46.2 LTS or later.

3

Which versions of Jenkins are affected by CVE-2017-1000353?

CVE-2017-1000353 affects Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier.

4

Can CVE-2017-1000353 be exploited remotely?

Yes, CVE-2017-1000353 can be exploited remotely by attackers without authentication.

5

Is there a workaround for CVE-2017-1000353?

There are no effective workarounds for CVE-2017-1000353; upgrading is the recommended course of action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203