Categories
CVE-2024-23900

Path Traversal in org.jenkins-ci.plugins:matrix-project (CVE-2024-23900)

Summary

Path traversal in org.jenkins-ci.plugins:matrix-project (CVE-2024-23900). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 822.824.v14451b or later.

Original description

The description as published by the source.

Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects, allowing attackers with Item/Configure permission to create or replace any config.xml files on the Jenkins controller file system with content not controllable by the attackers.

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-23900 has been found in org.jenkins-ci.plugins:matrix-project.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.plugins:matrix-project to 822.824.v14451b or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:matrix-project CVE-2024-23900" on the vendor's site.

CVE-2024-23900 (org.jenkins-ci.plugins:matrix-project) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 822.824.v14451b — 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.plugins:matrix-project.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:matrix-project.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 822.824.v14451b.

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

  2. 2
    Apply patch patch
    Upgrade org.jenkins-ci.plugins:matrix-project to 822.824.v14451b

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

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

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

Affected packages

Maven org.jenkins-ci.plugins:matrix-project
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"822.824.v14451b"}]}]

References

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