Skip to content

← Public intelligence

Maven package

org.jenkins-ci.main:remoting

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1MavenPublished

    Jenkins Remoting library arbitrary file read vulnerability

    CVE-2024-43044 · GHSA-h856-ffvv-xvr4

    Affected
    • Maven org.jenkins-ci.main:remoting < 3206.3208; >= 3248, < 3248.3250; >= 3256, < 3256.3258
    Fixed in
    3206.32083248.32503256.3258· Vendor fix available
    Issue
    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.v88af6e922152 and earlier, except 3206.3208.v409508a675ff and 3248.3250.v3277a8e88c9b, 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…

    Recommended action: Upgrade to 3256.3258, 3248.3250 or 3206.3208 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →