Homepage

Out-of-bounds Read Affecting curl package, versions <0:7.53.1-14.81.amzn1

Severity

 Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.65% (81st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN201803-CURL-1711159
  • published27 Sept 2021
  • disclosed24 Jan 2018
Report a new vulnerability Found a mistake?

Introduced: 24 Jan 2018

CVE-2018-1000005  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2018.03 curl to version 0:7.53.1-14.81.amzn1 or higher.
This issue was patched in ALAS-2018-951.

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

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.