dbcve.org
JenkinsApplication

CVE-2023-27904

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to 2.375.4 / 2.394 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins 2.393 and earlier, LTS 2.375.3 and earlier 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins versions 2.393 and earlier, LTS 2.375.3 and earlier print full error stack traces on agent-related pages when agent connections are broken. This exposes internal configuration details, file paths, system architecture, and potentially plugin information that would otherwise be inaccessible to unauthenticated attackers.

MitigationUpgrade Jenkins to version 2.394 or later (or LTS 2.375.4 or later) to obtain the patched version that handles errors without exposing stack traces. As a workaround, restrict network access to agent-related pages until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 2.375.4< 2.394

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or append /api/json?tree=number to your Jenkins URL, or run: java -jar jenkins.war --version
    Affected if The version is earlier than 2.394 (weekly) or earlier than 2.375.4 (LTS)
  2. Verify if Jenkins agents are configured
    Navigate to Manage Jenkins > Manage Nodes or check /manage/nodes/
    Affected if There are configured agents or clouds connected to this Jenkins instance
  3. Check if agent-related pages are network-accessible
    Attempt to access the Manage Nodes page or individual agent pages from an unauthenticated context, or review network firewall/proxy rules
    Affected if Agent-related URLs are reachable without authentication from external networks
  4. Simulate broken agent connection to observe error behavior
    Temporarily disconnect an agent (if any are online) or introduce a network condition that breaks agent communication, then access the agent page
    Affected if The error page displays a full Java stack trace rather than a generic error message

You are affected if your Jenkins version is below 2.394 (or below 2.375.4 LTS) and you have agents configured, as broken agent connections will expose detailed stack traces to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.375.4 / 2.394 or later
Fixed in 2.375.42.394
Interim mitigation

Upgrade Jenkins to version 2.394 or later (or LTS 2.375.4 or later) to obtain the patched version that handles errors without exposing stack traces. As a workaround, restrict network access to agent-related pages until the upgrade can be performed.

Recommended fix High confidence

Jenkins 2.394 (weekly) or Jenkins LTS 2.375.4

  1. Plan and schedule a maintenance window for the Jenkins upgrade
  2. Back up Jenkins home directory, configuration, and any plugins
  3. Stop the Jenkins service
  4. Upgrade Jenkins to version 2.394 (weekly release) OR Jenkins LTS 2.375.4
  5. Start the Jenkins service and verify the application is running
  6. Confirm the fix by accessing agent-related pages to ensure error stack traces are no longer exposed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27904 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data