Cross-Site Scripting (XSS) in org.jenkins-ci.main:jenkins-core (CVE-2023-27898)
Summary
Cross-site scripting in org.jenkins-ci.main:jenkins-core (CVE-2023-27898). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.375.4 or later.
Original description
The description as published by the source.
Jenkins LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances.
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-2023-27898 has been found in org.jenkins-ci.main:jenkins-core.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.375.4 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2023-27898" on the vendor's site.
CVE-2023-27898 (org.jenkins-ci.main:jenkins-core) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.375.4 — 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.
Cross-site scripting (XSS) (CWE-79) exists in org.jenkins-ci.main:jenkins-core.
Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.375.4.
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.375.4ステージング環境で 2.375.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory jenkins.io
- web nvd.nist.gov
- web github.com