dbcve.org
JenkinsApplication

CVE-2024-43044

HIGH · 8.8 CVSS v3.1 Published 2024-08-07
Fix available
A fix is available. Upgrade to 2.452.4 / 2.471 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins 2.470 and earlier, LTS 2.452.3 and earlier allows agent processes to read arbitrary files from the Jenkins controller file system by using the `ClassLoaderProxy#fetchJar` method in the Remoting library.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins agent processes can read arbitrary files from the controller file system by exploiting the ClassLoaderProxy#fetchJar method in the Remoting library, allowing unauthorized file disclosure on the Jenkins controller.

MitigationUpgrade Jenkins to version 2.471 or later (or LTS 2.452.4 or later) to patch the ClassLoaderProxy#fetchJar vulnerability in the Remoting library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 2.452.4< 2.471

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins or run: java -jar jenkins.war --version (or check the version displayed in the UI footer)
    Affected if Version is less than 2.452.4 (LTS) or less than 2.471 (weekly)
  2. Verify Remoting library is in use
    Check if agents are configured and connected: Manage Jenkins > Nodes > [check for any agents]. The vulnerability exploits the ClassLoaderProxy#fetchJar method in Remoting, which handles agent-controller communication.
    Affected if Any agents (permanent or temporary) are connected to the controller
  3. Confirm Remoting library version
    Locate the remoting.jar file in the Jenkins installation (typically in $JENKINS_HOME/war/WEB-INF/lib/ or within the jenkins.war), or check the bundled Remoting version in Manage Jenkins > System Information > Remoting Version
    Affected if Remoting version is below the version that includes the fix (corresponding to Jenkins 2.452.4/2.471)

You are affected if your Jenkins version is below 2.452.4 (LTS) or below 2.471 (weekly) and you have any agent nodes connected to the controller.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.452.4 / 2.471 or later
Fixed in 2.452.42.471
Interim mitigation

Upgrade Jenkins to version 2.471 or later (or LTS 2.452.4 or later) to patch the ClassLoaderProxy#fetchJar vulnerability in the Remoting library.

Recommended fix High confidence

Jenkins 2.452.4 (LTS) or Jenkins 2.471 (weekly)

  1. 1. Backup the Jenkins home directory (JENKINS_HOME) including all configurations, jobs, and plugin data
  2. 2. Review the Jenkins LTS upgrade guide and check plugin compatibility with the target version
  3. 3. Download Jenkins 2.452.4 LTS (for LTS users) or Jenkins 2.471 (for weekly users) from https://www.jenkins.io/download/
  4. 4. Stop the Jenkins service
  5. 5. Replace the existing jenkins.war file or update via your package manager (apt, yum, Docker, etc.)
  6. 6. Start the Jenkins service
  7. 7. Verify the upgrade by checking the Jenkins version at: Manage Jenkins > About Jenkins
  8. 8. Ensure critical jobs and plugins function correctly after upgrade
Caveat Major plugin incompatibilities may occur; test in staging first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43044 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data