CVE-2017-15118
CVE-2017-15118 Vulnerability Analysis & Exploit Intelligence
A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu before 2.11 allowing a client to request an export name of size up to 4096 bytes, which in fact should be limited to 256 bytes, causing an out-of-bounds stack write in the qemu process. If NBD server requires TLS, the attacker cannot trigger the buffer overflow without first successfully negotiating TLS.
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
Exploit code
public exploit, none observed
EPSS
12%
chance of exploitation in 30 days
CVSS base
8.3
HIGH
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 |
|---|---|---|---|---|---|
| 8.3 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-121
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Indexed by
References
7 on the record
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-15118
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:1104
vendor-advisory, x_refsource_REDHAT
- lists.gnu.org/archive/html/qemu-devel/2017-11/msg05045.html
x_refsource_MISC
- usn.ubuntu.com/3575-1/
vendor-advisory, x_refsource_UBUNTU
- www.securityfocus.com/bid/101975
vdb-entry, x_refsource_BID
- www.openwall.com/lists/oss-security/2017/11/28/8
x_refsource_MISC
- www.exploit-db.com/exploits/43194/
exploit, x_refsource_EXPLOIT-DB
Elsewhere on this site
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.