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.
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
The product writes data past the end, or before the beginning, of the intended buffer.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-15118 | issue tracking third party advisory patch |
| https://access.redhat.com/errata/RHSA-2018:1104 | third party advisory vendor advisory |
| https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg05045.html | exploit third party advisory patch |
| https://usn.ubuntu.com/3575-1/ | third party advisory vendor advisory |
| http://www.securityfocus.com/bid/101975 | vdb entry third party advisory |
| http://www.openwall.com/lists/oss-security/2017/11/28/8 | mailing list third party advisory patch |
| https://www.exploit-db.com/exploits/43194/ | exploit vdb entry third party advisory |