CVE Feed

    Dashboard / CVE / CVE-2016-8618

    CVE-2016-8618

    The libcurl API function called `curl_maprintf()` before version 7.51.0 can be tricked into doing a double-free due to an unsafe `size_t` multiplication, on systems using 32 bit `size_t` variables.

    Published:Nov 2, 2016
    Last Modified:Nov 21, 2024
    EPS:Jul 31, 2018
    EPSS Score:0.01582
    CVSS Score:5.3

    Affected Products

    Vendor
    Haxx
    Product
    Curl
    Vendor
    Redhat
    Product
    Jboss Core Services
    Vendor
    Redhat
    Product
    Rhel Software Collections

    Exploits

    No exploit reference

    Common Attack Pattern Enumeration and Classification (CAPEC)

    No CAPEC recorded yet

    Related CVEs

    CVE-2026-7168 (CVSS 5.3) — Successfully using libcurl to do a transfer over a specific HTTP proxy (`proxyA`) with **Digest** authenticati…
    CVE-2026-7009 (CVSS 5.3) — When curl is told to use the Certificate Status Request TLS extension, often referred to as *OCSP stapling*, t…
    CVE-2026-6429 (CVSS 5.3) — When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, libcurl could leak the pa…
    CVE-2026-4873 (CVSS 5.9) — A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection …
    CVE-2026-6253 (CVSS 5.9) — curl might erroneously pass on credentials for a first proxy to a second proxy. This can happen when the foll…
    CVE-2026-5773 (CVSS 7.5) — libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers. libcurl features a pool …
    CVE-2026-5545 (CVSS 6.5) — libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) reque…
    CVE-2026-6276 (CVSS 7.5) — Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is subsequen…
    CVE-2026-3805 (CVSS 7.5) — When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into al…
    CVE-2026-3784 (CVSS 6.5) — curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request …

    References

    http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
    http://www.securityfocus.com/bid/94098
    http://www.securitytracker.com/id/1037192
    https://access.redhat.com/errata/RHSA-2018:2486
    https://access.redhat.com/errata/RHSA-2018:3558
    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8618
    https://curl.haxx.se/docs/adv_20161102D.html
    https://security.gentoo.org/glsa/201701-47
    https://www.tenable.com/security/tns-2016-21
    http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
    http://www.securityfocus.com/bid/94098
    http://www.securitytracker.com/id/1037192
    https://access.redhat.com/errata/RHSA-2018:2486
    https://access.redhat.com/errata/RHSA-2018:3558
    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8618
    https://curl.haxx.se/docs/adv_20161102D.html
    https://security.gentoo.org/glsa/201701-47
    https://www.tenable.com/security/tns-2016-21

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High