CVE-2017-1000353: Deserialization of Untrusted Data in Jenkins

CVE-2017-1000353 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2022-05-13

Jenkins, a widely used automation server for software development, contains a critical security flaw that allows unauthorized individuals to take complete control of the server. By sending a specially crafted command to the Jenkins command-line interface, an attacker can execute arbitrary code without needing a username or password. This could lead to the theft of sensitive source code, disruption of software delivery pipelines, or the use of the server as a foothold for further attacks within the corporate network.

Technologies: Jenkins, org.jenkins-ci.main:jenkins-core (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2017-1000353 exploited in the wild?
Yes. CVE-2017-1000353 is known to be exploited in the wild, first recorded on 2 October 2025. Treat it as urgent.
How severe is CVE-2017-1000353?
Critical severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?
Jenkins 2.56 and earlier, 2.46.1 LTS and earlier; org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=2.50,fixed=2.57.
Is there a fix for CVE-2017-1000353?
Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-1000353 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2017-1000353?
Check whether you run Jenkins or org.jenkins-ci.main:jenkins-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.57 or later
    # set org.jenkins-ci.main:jenkins-core to 2.57 in your pom.xml or build.gradle

Technical details

A remote code execution vulnerability exists in Jenkins due to the improper deserialization of untrusted data within the Jenkins CLI. The vulnerability stems from the CLI's use of a remoting-based protocol that utilizes Java serialization. An unauthenticated attacker can bypass existing blocklist protections by transferring a serialized Java 'SignedObject' object, which is then deserialized using a new 'ObjectInputStream'. This bypass allows for arbitrary code execution on the Jenkins controller. The issue is addressed in Jenkins 2.57 and 2.46.2 LTS by adding 'SignedObject' to the blocklist and deprecating the remoting-based CLI protocol in favor of a new HTTP-based protocol.

Affected products

  • Jenkins Jenkins 2.56 and earlier, 2.46.1 LTS and earlier

Identifiers

  • CVE-2017-1000353
  • GHSA-26wc-3wqp-g3rp

Timeline

  • 2017-04-26: advisory: Original vendor advisory published by Jenkins
  • 2025-10-02: kev added: Added to CISA Known Exploited Vulnerabilities catalog
  • 2025-10-02: exploited: Confirmed as exploited in the wild per CISA KEV entry

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.