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.
packetstormsecurity.com/files/159266/Jenkins-2.56-CLI-Deserialization-Code-Execution.html
www.securityfocus.com/bid/98056
github.com/jenkinsci/jenkins
github.com/jenkinsci/jenkins/commit/36b8285a41eb28333549e8d851f81fd80a184076
github.com/jenkinsci/jenkins/commit/f237601afd750a0eaaf961e8120b08de238f2c3f
jenkins.io/security/advisory/2017-04-26
nvd.nist.gov/vuln/detail/CVE-2017-1000353
www.exploit-db.com/exploits/41965
www.oracle.com/security-alerts/cpuapr2022.html