Vulnerability Details : CVE-2018-14618

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.)
Vulnerability category: Overflow
Published 2018-09-05 19:29:00
Updated 2019-04-22 17:48:01
Source Red Hat, Inc.
View at NVD,

Exploit prediction scoring system (EPSS) score for CVE-2018-14618

Probability of exploitation activity in the next 30 days: 1.77%

Percentile, the proportion of vulnerabilities that are scored at or less: ~ 86 % EPSS Score History EPSS FAQ

CVSS scores for CVE-2018-14618

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Source

CWE ids for CVE-2018-14618

  • A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
    Assigned by: (Secondary)
  • The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
    Assigned by: (Secondary)
  • The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.
    Assigned by: (Primary)

References for CVE-2018-14618

Products affected by CVE-2018-14618

This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to terms of use!