CVE-2017-15118

HIGHCVSS 8.3/10EPSS 11.93%

Last modified

CVE-2017-15118 is a high-severity vulnerability rated 8.3/10 on the CVSS scale. 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.. EPSS estimates a 11.93% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.0
8.3/10

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

EPSS Probability
11.93%

95.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
QemuQemu< 2.11
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux16.04
CanonicalUbuntu Linux17.10
RedhatEnterprise Linux7.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-15118?
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.
How severe is CVE-2017-15118?
CVE-2017-15118 has a CVSS score of 8.3/10 (HIGH severity). The EPSS model estimates a 11.93% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15118?
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.

How Strix Helps

Related CVEs from 2017

Are you affected by CVE-2017-15118?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST