diff options
author | Wolfgang Bumiller <w.bumiller@proxmox.com> | 2016-01-12 13:52:39 +0100 |
---|---|---|
committer | Timothy Pearson <tpearson@raptorengineering.com> | 2019-11-29 19:28:24 -0600 |
commit | 02c035dba46aa139d9b459f9735d661c420d8d28 (patch) | |
tree | d64a090360746552dcaa9d81807f7f9f4427e918 /hw/mem | |
parent | fe205d0b576d819ddd2964fab7bc14f8aec79c9f (diff) | |
download | hqemu-02c035dba46aa139d9b459f9735d661c420d8d28.zip hqemu-02c035dba46aa139d9b459f9735d661c420d8d28.tar.gz |
vnc: clear vs->tlscreds after unparenting it
This pointer should be cleared in vnc_display_close()
otherwise a use-after-free can happen when when using the
old style 'x509' and 'tls' options rather than a persistent
tls-creds -object, by issuing monitor commands to change
the vnc server like so:
Start with: -vnc unix:test.socket,x509,tls
Then use the following monitor command:
change vnc unix:test.socket
After this the pointer is still set but invalid and a crash
can be triggered for instance by issuing the same command a
second time which will try to object_unparent() the same
pointer again.
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/mem')
0 files changed, 0 insertions, 0 deletions