Vulnerabilidades do Jenkins Jenkins

Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system.

Existe uma vulnerabilidade de execução de código no framework web Stapler usado pelo Jenkins 2.153 e anteriores, e pelo LTS 2.138.3 e anteriores, em stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java, que permite a atacantes invocar alguns métodos em objetos Java ao acessar URLs criadas de forma específica que não deveriam ser invocadas dessa maneira.

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.