Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2023-27904)

Summary

Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2023-27904). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.394 or later.

Original description

The description as published by the source.

Jenkins 2.393 and earlier, LTS 2.375.3 and earlier, and prior to LTS 2.387.1 prints an error stack trace on agent-related pages when agent connections are broken, potentially revealing information about Jenkins configuration that is otherwise inaccessible to attackers.

Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 does not display error stack traces when agent connections are broken.

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-27904 has been found in org.jenkins-ci.main:jenkins-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.394 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2023-27904" on the vendor's site.

CVE-2023-27904 (org.jenkins-ci.main:jenkins-core)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.394 — 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

A vulnerability (unclassified) 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: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.394.

🛡️ 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
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで org.jenkins-ci.main:jenkins-core を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade org.jenkins-ci.main:jenkins-core to 2.394
```
ステージング環境で 2.394 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
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.388"},{"fixed":"2.394"}]}]