Information Exposure Affecting curl package, versions <0:7.51.0-9.75.amzn1


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.24% (64th 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-1708243
  • published27 Sept 2021
  • disclosed5 Oct 2017

Introduced: 5 Oct 2017

CVE-2017-1000099  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2018.03 curl to version 0:7.51.0-9.75.amzn1 or higher.
This issue was patched in ALAS-2017-889.

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.

When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory.