dbcve.org
TomcatWeb server / proxy · Apache

CVE-2017-5651

CRITICAL · 9.8 CVSS v3.0 Published 2017-04-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the refactoring of the HTTP connectors introduced a regression in the send file processing. If the send file processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This could result in the same Processor being used for multiple requests which in turn could lead to unexpected errors and/or response mix-up.

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

A detailed technical summary for this CVE is being prepared.

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
TomcatWeb server / proxy
Affected:= 8.5.0= 8.5.1= 8.5.2= 8.5.3= 8.5.4= 8.5.5= 8.5.6= 8.5.7= 8.5.8= 8.5.9= 8.5.10= 8.5.11

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

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

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
Patch available Apply the vendor patch
Vendor patch bz.apache.org →
Recommended fix High confidence

Tomcat 8.5.13 or later (or Tomcat 9.0.0.M19+ if upgrading to Tomcat 9)

  1. 1. Download Apache Tomcat 8.5.13 or later from the official Apache Tomcat website (https://tomcat.apache.org/)
  2. 2. Stop the affected Tomcat server
  3. 3. Back up the current Tomcat installation directory, including all configuration files and deployed applications
  4. 4. Extract the new Tomcat 8.5.13+ version to replace the existing installation
  5. 5. Restore your configuration files (server.xml, context.xml, etc.) from the backup, or carefully merge any necessary changes
  6. 6. Redeploy all applications from the backup to the new Tomcat installation
  7. 7. Start the Tomcat server and verify the application is functioning correctly
  8. 8. Monitor logs for any errors related to request processing or send file operations
Caveat Minor: Review release notes for any configuration changes between 8.5.x versions; ensure custom connector configurations are compatible

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

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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