Homepage

Incorrect Calculation of Buffer Size The advisory has been revoked - it doesn't affect any version of package rh-dotnetcore11-curl.src  (opens in a new tab)

Threat Intelligence

EPSS
0.49% (66th 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-RHEL10-RHDOTNETCORE11CURLSRC-15324700
  • published21 Feb 2026
  • disclosed5 Sept 2018
Report a new vulnerability Found a mistake?

Introduced: 5 Sep 2018

CVE-2018-14618  (opens in a new tab)
CWE-131  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rh-dotnetcore11-curl.src package and not the rh-dotnetcore11-curl.src package as distributed by RHEL.

curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)