First published: Mon Jan 29 2018(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins LTS | <=2.56 | |
Jenkins LTS | <=2.46.1 | |
Oracle Communications Cloud Native Core Automated Test Suite | =1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000353 has been classified as a critical vulnerability due to its potential for unauthenticated remote code execution.
To fix CVE-2017-1000353, update Jenkins to version 2.60 or later, or 2.46.2 LTS or later.
CVE-2017-1000353 affects Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier.
Yes, CVE-2017-1000353 can be exploited remotely by attackers without authentication.
There are no effective workarounds for CVE-2017-1000353; upgrading is the recommended course of action.