Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2024-47803)
Summary
Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2024-47803). Risk of unauthorized operations or information disclosure. Exploitable via secretTextarea. Mitigation: upgrade to 2.479 or later.
Original description
The description as published by the source.
Jenkins LTS 2.462.2 and earlier does not redact multi-line secret values in error messages generated for form submissions involving the secretTextarea form field.
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-47803 has been found in org.jenkins-ci.main:jenkins-core.
Attackers can target a specific entry point like secretTextarea over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.479 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2024-47803" on the vendor's site.
CVE-2024-47803 (org.jenkins-ci.main:jenkins-core) — CWE-209
Attack vector: remote (network-reachable) / no user interaction
Attack surface: secretTextarea
Patched: 2.479 — 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.
A vulnerability (CWE-209) exists in org.jenkins-ci.main:jenkins-core. Attackers reach the vulnerable code path via secretTextarea.
Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core. Attack surface: secretTextarea.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.479.
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.main:jenkins-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.main:jenkins-core to 2.479ステージング環境で 2.479 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory jenkins.io
- web nvd.nist.gov