CVE-2016-8618
UnknownEPSS 4.57%
Last modified
CVE-2016-8618 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 4.57% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Haxx | Curl | < 7.51.0 |
References
- http://www.securityfocus.com/bid/94098Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037192Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2486Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8618Issue Tracking, Patch, Third Party Advisory
- https://curl.haxx.se/docs/adv_20161102D.htmlPatch, Vendor Advisory
- https://security.gentoo.org/glsa/201701-47Third Party Advisory
- https://www.tenable.com/security/tns-2016-21Third Party Advisory
- http://www.securityfocus.com/bid/94098Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037192Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2486Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8618Issue Tracking, Patch, Third Party Advisory
- https://curl.haxx.se/docs/adv_20161102D.htmlPatch, Vendor Advisory
- https://security.gentoo.org/glsa/201701-47Third Party Advisory
- https://www.tenable.com/security/tns-2016-21Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is 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.
How severe is CVE-2016-8618?
Severity scoring for CVE-2016-8618 is pending analysis. The EPSS model estimates a 4.57% probability of exploitation in the next 30 days.
How do I fix CVE-2016-8618?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2016-8618?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST