Homepage

Out-of-bounds Read Affecting libcurl package, versions <0:7.29.0-42.el7_4.1

Severity

 Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
2.19% (90th 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-CENTOS7-LIBCURL-2095007
  • published26 Jul 2021
  • disclosed23 Oct 2017
Report a new vulnerability Found a mistake?

Introduced: 23 Oct 2017

CVE-2017-1000257  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Centos:7 libcurl to version 0:7.29.0-42.el7_4.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invokes strlen() on the data to figure out the length. The strlen() is called on a heap based buffer that might not be zero terminated so libcurl might read beyond the end of it into whatever memory lies after (or just crash) and then deliver that to the application as if it was actually downloaded.