Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-43044

Path Traversal in org.jenkins-ci.main:remoting (CVE-2024-43044)

Summary

Path traversal in org.jenkins-ci.main:remoting (CVE-2024-43044). Successful exploitation can lead to full system takeover. Exploitable via agent.jar. Mitigation: upgrade to 3256.3258 or later.

Original description

The description as published by the source.

Jenkins 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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-43044 has been found in org.jenkins-ci.main:remoting.
Attackers can target a specific entry point like agent.jar over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.jenkins-ci.main:remoting to 3256.3258 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:remoting CVE-2024-43044" on the vendor's site.

CVE-2024-43044 (org.jenkins-ci.main:remoting) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: agent.jar / remoting.jar
Patched: 3256.3258 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in org.jenkins-ci.main:remoting. Attackers reach the vulnerable code path via agent.jar without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.main:remoting. Attack surface: agent.jar / remoting.jar.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3256.3258.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.jenkins-ci.main:remoting を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.jenkins-ci.main:remoting to 3256.3258

    ステージング環境で 3256.3258 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.jenkins-ci.main:remoting
[{"type":"ECOSYSTEM","events":[{"introduced":"3256"},{"fixed":"3256.3258"}]}]
Maven org.jenkins-ci.main:jenkins-core
[{"type":"ECOSYSTEM","events":[{"introduced":"2.470"},{"fixed":"2.471"}]}]
Bitnami jenkins
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.462.1"},{"introduced":"2.463.0"},{"fixed":"2.479.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details