CVE-2024-43044

Jenkins uses the Remoting library (typically agent.jar or remoting.jar) for the communication between controller and agents. This library allows agents to load classes and classloader resources from the controller, so that Java objects sent from the controller (build steps, etc.) can be executed on agents.

In addition to individual class and resource files, Remoting also allows Jenkins plugins to transmit entire jar files to agents using the Channel#preloadJar API. As of publication of this advisory, this feature is used by the following plugins distributed by the Jenkins project: bouncycastle API, Groovy, Ivy, TeamConcert

In Remoting 3256.v88a_f6e922152 and earlier, except 3206.3208.v409508a_675ff and 3248.3250.v3277a_8e88c9b_, included in Jenkins 2.470 and earlier, LTS 2.452.3 and earlier, calls to Channel#preloadJar result in the retrieval of files from the controller by the agent using ClassLoaderProxy#fetchJar. Additionally, the implementation of ClassLoaderProxy#fetchJar invoked on the controller does not restrict paths that agents could request to read from the controller file system.

This allows agent processes, code running on agents, and attackers with Agent/Connect permission to read arbitrary files from the Jenkins controller file system.

The Remoting library in Jenkins 2.471, LTS 2.452.4, LTS 2.462.1 now sends jar file contents with Channel#preloadJar requests, the only use case of ClassLoaderProxy#fetchJar in agents, so that agents do not need to request jar file contents from controllers anymore.

To retain compatibility with older versions of Remoting in combination with the plugins listed above, ClassLoaderProxy#fetchJar is retained and otherwise unused, just deprecated. Its implementation in Jenkins 2.471, LTS 2.452.4, LTS 2.462.1 was changed so that it is now limited to retrieving jar files referenced in the core classloader or any plugin classloader.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-43044 has a CVSS score of 9.0 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3206.3208, 3248.3250, 3256.3258, 2.452.4, 2.462.1, 2.471); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-43044? CVE-2024-43044 is a high-severity path traversal vulnerability in org.jenkins-ci.main:remoting (maven), affecting versions < 3206.3208. It is fixed in 3206.3208, 3248.3250, 3256.3258, 2.452.4, 2.462.1, 2.471. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2024-43044? CVE-2024-43044 has a CVSS score of 9.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-43044?
   • org.jenkins-ci.main:remoting (maven) (versions < 3206.3208)
   • org.jenkins-ci.main:jenkins-core (maven) (versions < 2.452.4)
4. Is there a fix for CVE-2024-43044? Yes. CVE-2024-43044 is fixed in 3206.3208, 3248.3250, 3256.3258, 2.452.4, 2.462.1, 2.471. Upgrade to this version or later.
5. Is CVE-2024-43044 exploitable, and should I be worried? Whether CVE-2024-43044 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-43044 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-43044?
   • Upgrade org.jenkins-ci.main:remoting to 3206.3208 or later
   • Upgrade org.jenkins-ci.main:remoting to 3248.3250 or later
   • Upgrade org.jenkins-ci.main:remoting to 3256.3258 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.452.4 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.462.1 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.471 or later