ghsa-cj8j-r7q8-xg4f
Vulnerability from github
Published
2022-05-14 00:58
Modified
2022-05-14 00:58
Severity ?
9.1 (Critical) - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Details

libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like : to the target buffer, while this was recently changed to : (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2018-1000005",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-125",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2018-01-24T22:29:00Z",
      severity: "CRITICAL",
   },
   details: "libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.",
   id: "GHSA-cj8j-r7q8-xg4f",
   modified: "2022-05-14T00:58:02Z",
   published: "2022-05-14T00:58:02Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2018-1000005",
      },
      {
         type: "WEB",
         url: "https://github.com/curl/curl/pull/2231",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2019:1543",
      },
      {
         type: "WEB",
         url: "https://curl.haxx.se/docs/adv_2018-824a.html",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/3554-1",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2018/dsa-4098",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1040273",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


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.