Information Disclosure in org.jenkins-ci.plugins:structs (CVE-2024-39458)
Summary
Vulnerability in org.jenkins-ci.plugins:structs (CVE-2024-39458). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 338.v848422169819 or later.
Original description
The description as published by the source.
When Jenkins Structs Plugin 337.v1b_04ea_4df7c8 and earlier fails to configure a build step, it logs a warning message containing diagnostic information that may contain secrets passed as step parameters, potentially resulting in accidental exposure of secrets through the default system log.
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-39458 has been found in org.jenkins-ci.plugins:structs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.plugins:structs to 338.v848422169819 or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:structs CVE-2024-39458" on the vendor's site.
CVE-2024-39458 (org.jenkins-ci.plugins:structs) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated
Patched: 338.v848422169819 — 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.
Information disclosure (CWE-200) exists in org.jenkins-ci.plugins:structs.
Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:structs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 338.v848422169819.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.jenkins-ci.plugins:structs を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.plugins:structs to 338.v848422169819ステージング環境で 338.v848422169819 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory jenkins.io
- package github.com
- web github.com
- web openwall.com