dbcve.org
JenkinsApplication

CVE-2023-27900

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 hudson.util.MultipartFormDataParser, 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 uses Apache Commons FileUpload library in hudson.util.MultipartFormDataParser without specifying limits for the number of request parts (introduced in version 1.5 for CVE-2023-24998). This allows remote attackers to cause denial of service by sending specially crafted multipart HTTP requests with excessive parts, exhausting server resources.

MitigationUpgrade Jenkins to version 2.394 or LTS 2.375.4 or later, which properly specify limits for request parts in the Apache Commons FileUpload library, preventing resource exhaustion attacks.

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. Check installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins or access /api/json?tree=version endpoint, or run 'java -jar jenkins.war --version' if running from WAR
    Affected if Version is less than 2.375.4 for LTS releases or less than 2.394 for weekly releases
  2. Verify MultipartFormDataParser is in use
    Search for imports or references to hudson.util.MultipartFormDataParser in deployed Jenkins plugins or custom code that handles file uploads
    Affected if Any plugin or custom code uses hudson.util.MultipartFormDataParser for processing multipart requests on affected Jenkins versions
  3. Confirm HTTP endpoint accepts multipart requests
    Review web requests to Jenkins that include Content-Type: multipart/form-data, typically used for file uploads, plugin uploads, or job configuration attachments
    Affected if Jenkins handles multipart HTTP requests on versions below 2.375.4 or 2.394, enabling resource exhaustion through excessive parts

Jenkins is affected if running version 2.375.3 or earlier (LTS) or 2.393 or earlier (weekly), and the server processes multipart HTTP requests.

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 limits for request parts in the Apache Commons FileUpload library, preventing resource exhaustion attacks.

Recommended fix High confidence

Jenkins 2.375.4 (LTS) or Jenkins 2.394+

  1. 1. Back up your Jenkins home directory (JENKINS_HOME) including all jobs, configurations, and plugin data.
  2. 2. Review plugin compatibility with the target Jenkins version before upgrading.
  3. 3. Download the Jenkins WAR file for the target version (2.375.4 LTS or 2.394+).
  4. 4. Stop the Jenkins service.
  5. 5. Replace the existing jenkins.war file in the Jenkins installation directory with the new version.
  6. 6. Start the Jenkins service.
  7. 7. Verify the upgrade by checking the Jenkins version at Manage Jenkins > About Jenkins.
  8. 8. Test critical jobs and pipelines to ensure normal operation.
Caveat Review plugin compatibility before upgrading; some plugins may require updates for the new Jenkins version

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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