ubuntu-cve-2018-1000005
Vulnerability from osv_ubuntu
Published
2018-01-24 00:00
Modified
2026-04-22 07:38
Summary
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.

Severity

{
  "affected": [
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "curl",
            "binary_version": "7.47.0-1ubuntu2.6"
          },
          {
            "binary_name": "libcurl3",
            "binary_version": "7.47.0-1ubuntu2.6"
          },
          {
            "binary_name": "libcurl3-gnutls",
            "binary_version": "7.47.0-1ubuntu2.6"
          },
          {
            "binary_name": "libcurl3-nss",
            "binary_version": "7.47.0-1ubuntu2.6"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "curl",
        "purl": "pkg:deb/ubuntu/curl@7.47.0-1ubuntu2.6?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.47.0-1ubuntu2.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "7.43.0-1ubuntu2",
        "7.45.0-1ubuntu1",
        "7.46.0-1ubuntu1",
        "7.47.0-1ubuntu1",
        "7.47.0-1ubuntu2",
        "7.47.0-1ubuntu2.1",
        "7.47.0-1ubuntu2.2",
        "7.47.0-1ubuntu2.3",
        "7.47.0-1ubuntu2.4",
        "7.47.0-1ubuntu2.5"
      ]
    }
  ],
  "aliases": [],
  "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\u0027t 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": "UBUNTU-CVE-2018-1000005",
  "modified": "2026-04-22T07:38:48Z",
  "published": "2018-01-24T00:00:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-1000005"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/curl/curl/pull/2231"
    },
    {
      "type": "REPORT",
      "url": "https://curl.haxx.se/docs/adv_2018-824a.html"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-3554-1"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2018-1000005"
    }
  ],
  "related": [
    "USN-3554-1"
  ],
  "schema_version": "1.7.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"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2018-1000005"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…