ghsa-6x9x-8qw9-9pp6
Vulnerability from github
Published
2018-10-19 16:16
Modified
2022-09-14 01:09
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)
Details

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), are vulnerable to HTTP Request Smuggling when presented with two content-lengths headers, allowing authorization bypass. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decides on the shorter length, but still passes on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary is imposing authorization, the fake pipelined request bypasses that authorization.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.eclipse.jetty:jetty-server",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "9.2.25.v20180606",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.eclipse.jetty:jetty-server",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.3.0",
                  },
                  {
                     fixed: "9.3.24.v20180605",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.eclipse.jetty:jetty-server",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.4.0",
                  },
                  {
                     fixed: "9.4.11.v20180605",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2017-7658",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-444",
      ],
      github_reviewed: true,
      github_reviewed_at: "2020-06-16T21:20:39Z",
      nvd_published_at: "2018-06-26T17:29:00Z",
      severity: "CRITICAL",
   },
   details: "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), are vulnerable to HTTP Request Smuggling when presented with two content-lengths headers, allowing authorization bypass. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decides on the shorter length, but still passes on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary is imposing authorization, the fake pipelined request bypasses that authorization.",
   id: "GHSA-6x9x-8qw9-9pp6",
   modified: "2022-09-14T01:09:24Z",
   published: "2018-10-19T16:16:38Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2017-7658",
      },
      {
         type: "WEB",
         url: "https://bugs.eclipse.org/bugs/show_bug.cgi?id=535669",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-6x9x-8qw9-9pp6",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@%3Cissues.activemq.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/9317fd092b257a0815434b116a8af8daea6e920b6673f4fd5583d5fe@%3Ccommits.druid.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/r41af10c4adec8d34a969abeb07fd0d6ad0c86768b751464f1cdd23e8@%3Ccommits.druid.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/r9159c9e7ec9eac1613da2dbaddbc15691a13d4dbb2c8be974f42e6ae@%3Ccommits.druid.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/ra6f956ed4ec2855583b2d0c8b4802b450f593d37b77509b48cd5d574@%3Ccommits.druid.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20181014-0001",
      },
      {
         type: "WEB",
         url: "https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbst03953en_us",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2018/dsa-4278",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpuoct2020.html",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/106566",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1041194",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.