Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-23897 CISA KEV high

[KEV] Path Traversal in org.jenkins-ci.main:jenkins-core (CVE-2024-23897)

Summary

Path traversal in org.jenkins-ci.main:jenkins-core (CVE-2024-23897). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 2.442 or later.

Original description

The description as published by the source.

Jenkins LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system.

Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV

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-23897 has been found in org.jenkins-ci.main:jenkins-core.
Successful exploitation can lead to full system takeover.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.442 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2024-23897" on the vendor's site.

CVE-2024-23897 (org.jenkins-ci.main:jenkins-core) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.442 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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:jenkins-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core.

🔥 Severity

Severity: High. Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to 2.442.

🛡️ 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:jenkins-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade org.jenkins-ci.main:jenkins-core to 2.442

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

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

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

Affected packages

Maven org.jenkins-ci.main:jenkins-core
[{"type":"ECOSYSTEM","events":[{"introduced":"2.441"},{"fixed":"2.442"}]}]
Bitnami jenkins
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.452.1"}]}]

References

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