Multiple use-after-free vulnerabilities in vnc.c in the VNC server in QEMU 0.10.6 and earlier might allow guest OS users to execute arbitrary code on the host OS by establishing a connection from a VNC client and then (1) disconnecting during data transfer, (2) sending a message using incorrect integer data types, or (3) using the Fuzzy Screen Mode protocol, related to double free vulnerabilities.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=501131 | issue tracking patch |
| http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=753b405331 | broken link exploit |
| http://www.openwall.com/lists/oss-security/2009/10/16/8 | mailing list patch |
| http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=198a0039c5 | broken link exploit |
| http://marc.info/?l=qemu-devel&m=124324043812915 | mailing list |
| https://bugzilla.redhat.com/show_bug.cgi?id=508567 | issue tracking |
| http://www.securityfocus.com/bid/36716 | vdb entry third party advisory broken link |
| http://rhn.redhat.com/errata/RHEA-2009-1272.html | third party advisory |
| http://www.openwall.com/lists/oss-security/2009/10/16/5 | mailing list patch |
| https://bugzilla.redhat.com/show_bug.cgi?id=505641 | issue tracking exploit |