CVE-2016-8625
CVE-2016-8625 Vulnerability Analysis & Exploit Intelligence
curl before version 7.51.0 uses outdated IDNA 2003 standard to handle International Domain Names and this may lead users to potentially and unknowingly issue network transfer requests to the wrong host.
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
4%
chance of exploitation in 30 days
CVSS base
5.3
MEDIUM
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 |
|---|---|---|---|---|---|
| 5.3 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-20
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
References
11 on the record
- www.securityfocus.com/bid/94107
vdb-entry, x_refsource_BID
- curl.haxx.se/CVE-2016-8625.patch
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:3558
vendor-advisory, x_refsource_REDHAT
- www.tenable.com/security/tns-2016-21
x_refsource_CONFIRM
- curl.haxx.se/docs/adv_20161102K.html
x_refsource_CONFIRM
- www.securitytracker.com/id/1037192
vdb-entry, x_refsource_SECTRACK
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8625
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:2486
vendor-advisory, x_refsource_REDHAT
Elsewhere on this site
- the curl projectevery CVE for this vendor
- CWE-20other 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.