dbcve.org
JenkinsApplication

CVE-2023-27901

HIGH · 7.5 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to 2.375.4 / 2.394 or later.
See remediation →
84/100
Remediation priority · High
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 uses the Apache Commons FileUpload library without specifying limits for the number of request parts introduced in version 1.5 for CVE-2023-24998 in org.kohsuke.stapler.RequestImpl, allowing attackers to trigger a denial of service.

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 use the Apache Commons FileUpload library in org.kohsuke.stapler.RequestImpl without specifying limits for the number of request parts. This allows remote attackers to trigger a denial of service by sending specially crafted file upload requests.

MitigationUpgrade Jenkins to version 2.394 or LTS 2.375.4 or later, which properly specify request part limits when using Apache Commons FileUpload 1.5+.

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
None
Integrity
None
Availability
High

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

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. Determine Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or inspect the jenkins.war file version, or check the startup log for the version number
    Affected if The installed version is below 2.394 for weekly releases or below 2.375.4 for LTS releases
  2. Verify Jenkins is network accessible
    Check the Jenkins bind address configuration in jenkins.xml or httpPort in config.xml, and review firewall rules or reverse proxy settings that expose Jenkins
    Affected if Jenkins is reachable from untrusted network segments (the flaw is remotely exploitable via HTTP requests)
  3. Confirm file upload functionality is enabled
    Review whether any jobs or plugins use file parameters or the file upload feature - check job configurations for 'File Parameter' build steps or inspect installed plugins for upload-related functionality
    Affected if File upload features are available or enabled in any job configuration
  4. Inspect Apache Commons FileUpload usage
    If you have access to the Jenkins source or can inspect the stapler-core library, verify that org.kohsuke.stapler.RequestImpl uses Apache Commons FileUpload without explicit part limits configured
    Affected if The code uses Apache Commons FileUpload in RequestImpl without specifying limits for request parts

You are affected if your Jenkins version is below 2.394 (weekly) or below 2.375.4 (LTS), the instance is network-accessible, and file upload functionality is available - all three conditions must be met for remote exploitation.

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 LTS 2.375.4 or later, which properly specify request part limits when using Apache Commons FileUpload 1.5+.

Recommended fix High confidence

Jenkins LTS 2.375.4+ or Jenkins weekly 2.394+

  1. Back up your Jenkins home directory and configuration before upgrading
  2. Download the appropriate Jenkins WAR file from the official Jenkins repository (https://get.jenkins.io/war/)
  3. Stop the Jenkins service
  4. Replace the existing jenkins.war file with the new version
  5. Restart the Jenkins service
  6. Verify the upgrade was successful by checking the Jenkins version in the UI or via the API

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27901 — 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-27901 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