dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-7658

CRITICAL · 9.8 CVSS v3.1 Published 2018-06-26
Fix available
A fix is available. Upgrade to 9.3.24 / 9.4.11 or later.
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 Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing authorization, the fake pipelined request would bypass that authorization.

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
Debian LinuxOperating system
Affected:= 9.0
JettyApplication
Affected:<= 9.2.26>= 9.3.0, < 9.3.24>= 9.4.0, < 9.4.11
Rest Data ServicesApplication
Affected:= 11.2.0.4= 12.1.0.2= 12.2.0.1= 18c
Retail Xstore PaymentApplication
Affected:= 3.3
Retail Xstore Point Of ServiceApplication
Affected:= 7.1= 15.0= 16.0= 17.0
Xp P9000 Command ViewApplication
Affected:>= 8.4.0-00, <= 8.6.2-00
E Series Santricity ManagementApplication
Affected:all versions
E Series Santricity Os ControllerApplication
Affected:>= 11.0, <= 11.50.1

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.1/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
Upgrade available Upgrade to 9.3.24 / 9.4.11 or later
Fixed in 9.3.249.4.11
Vendor patch www.oracle.com →
Recommended fix High confidence

Jetty 9.4.11+ (or 9.3.24+ for 9.3.x branch, or 9.2.27+ for 9.2.x branch)

  1. 1. Identify the exact Jetty version currently deployed using the application's dependency management or by checking the jetty-version-maven-plugin output
  2. 2. For Jetty 9.4.x: upgrade to version 9.4.11 or later (9.4.12+, 9.4.13+, etc.)
  3. 3. For Jetty 9.3.x: upgrade to version 9.3.24 or later
  4. 4. For Jetty 9.2.x: upgrade to version 9.2.27 or later
  5. 5. If using a Debian system with Jetty (version 9.0), upgrade the entire Debian distribution or manually upgrade Jetty to a supported version
  6. 6. For other affected products (Oracle, Xp P9000, E Series), apply vendor-specific patches from the Oracle January 2019 CPU or contact the respective vendor
  7. 7. Rebuild and redeploy the application with the updated Jetty dependencies
  8. 8. Verify the fix by testing with malformed HTTP requests containing multiple content-length headers to confirm proper rejection
Caveat Minor: Very few breaking changes between patch versions; however, always test application functionality after upgrading Jetty as minor behavioral changes may exist

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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