CVE-2016-8617
CVE-2016-8617 Vulnerability Analysis & Exploit Intelligence
The base64 encode function in curl before version 7.51.0 is prone to a buffer being under allocated in 32bit systems if it receives at least 1Gb as input via `CURLOPT_USERNAME`.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
1%
chance of exploitation in 30 days
CVSS base
3.3
LOW
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 3.3 | CVSS 3.0 | LOW | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-787
References
12 on the record
- curl.haxx.se/docs/adv_20161102C.html
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:3558
vendor-advisory, x_refsource_REDHAT
- curl.haxx.se/CVE-2016-8617.patch
x_refsource_CONFIRM
- www.securityfocus.com/bid/94097
vdb-entry, x_refsource_BID
- www.tenable.com/security/tns-2016-21
x_refsource_CONFIRM
- www.securitytracker.com/id/1037192
vdb-entry, x_refsource_SECTRACK
- www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
x_refsource_CONFIRM
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8617
x_refsource_CONFIRM
Elsewhere on this site
- the curl projectevery CVE for this vendor
- CWE-787other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.