Security researchers have recently identified two critical vulnerabilities in Jenkins, a widely-used open-source automation server crucial for automating software development processes. The first vulnerability, tracked as CVE-2024-43044, affects Jenkins versions 2.470 and earlier, including LTS versions 2.452.3 and earlier. This flaw resides in the Remoting library, which facilitates communication between agents and the Jenkins controller. The vulnerability allows attackers with Agent/Connect permissions to read arbitrary files from the Jenkins controller file system due to insufficient path restrictions in the ClassLoaderProxy#fetchJar method. This exposure could potentially enable remote code execution (RCE), leading to significant security risks and system compromise.
The second vulnerability, CVE-2024-43045, also impacts Jenkins versions 2.470 and earlier, including LTS versions 2.452.3 and earlier. Discovered in the HTTP endpoint handling user permissions, this flaw results from a missing permission check. Attackers with Overall/Read permissions can access other users’ “My Views,” while those with global View/Configure and View/Delete permissions can modify these views. This medium-severity vulnerability could compromise user privacy and allow unauthorized changes to user settings.
Jenkins developers have addressed these security issues by releasing patches in the latest versions of the software. Users are advised to upgrade their installations to Jenkins version 2.471 for weekly releases or versions 2.452.4 and 2.462.1 for LTS releases. These updates include fixes for both vulnerabilities, ensuring that affected systems are protected against potential exploits.
In light of these findings, Jenkins users should promptly apply the recommended updates to secure their environments. The vulnerabilities underscore the importance of regular software updates and vigilant security practices to safeguard against emerging threats. Jenkins maintains its commitment to enhancing security and encourages users to stay informed about future updates and best practices for maintaining a secure automation infrastructure.
Reference:
