| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 02_server_sm-disable.patch | no | |||||
| 11_hurd_maxhostnamelen.patch | no | |||||
| 0003-Return-error-if-X11-is-not-detected.patch | Return error if X11 is not detected Vino-server crashes on Wayland in XQueryExtension. Since vino-server is not expected to work on displays other than X11, let's exit immediately if GDK_IS_X11_DISPLAY fail. https://bugzilla.gnome.org/show_bug.cgi?id=761120 |
Ondrej Holy <oholy@redhat.com> | no | 2018-02-20 | ||
| 0004-Don-t-install-the-D-Bus-service-file-when-Telepathy-.patch | Don't install the D-Bus service file when Telepathy is disabled The org.freedesktop.Telepathy.Client.Vino service is necessary for Vino to act as a Telepathy client, and is not useful without Telepathy. https://gitlab.gnome.org/GNOME/vino/merge_requests/3 |
Debarshi Ray <debarshir@gnome.org> | no | 2018-08-14 | ||
| 0005-Do-not-restart-service-after-unclean-exit-code.patch | Do not restart service after unclean exit code Currently, the vino-server.service has Restart=on-failure, which means that it is restarted in abnormal cases, but also in case of non-zero exit code. It is restarted 5 times e.g. in case when X11 is not detected, which doesn't make sense. Non-zero exit code is used only for states which won't change with restart (invalid commandline, wayland and some sanity checks). Change the value to Restart=on-abnormal in order to prevent the useless restarts and to not spam journal. https://bugzilla.gnome.org/show_bug.cgi?id=761120 |
Ondrej Holy <oholy@redhat.com> | no | 2018-05-22 | ||
| 0006-Do-not-listen-all-if-invalid-interface-is-provided.patch | Do not listen all if invalid interface is provided It is not a good idea from security point of view to listen all interfaces in case of invalid interface is provided. We should rather listen to nothing and print error in journal. https://bugzilla.gnome.org/show_bug.cgi?id=796349 |
Ondrej Holy <oholy@redhat.com> | no | 2018-05-22 | ||
| 0007-Prevent-monitoring-all-interfaces-after-change-of-ot.patch | Prevent monitoring all interfaces after change of other props Commit bfa1432 prevents monitoring all interfaces if invalid interface is provided, but it works only in some cases, because the invalid interface is not remembered and for example consequent change of port will cause that all interfaces are monitored again. Remember the invalid interface to prevent monitoring all interfaces even after change of other properties... https://bugzilla.gnome.org/show_bug.cgi?id=796349 |
Ondrej Holy <oholy@redhat.com> | no | 2018-08-24 | ||
| 0008-Properly-remove-watches-when-changing-server-props.patch | Properly remove watches when changing server props vino_server_init_io_channels calls vino_server_deinit_io_channels at the beginning, however the watches and channels don't have to be removed respective closed, because it relies on rfbListenSock array, which can be already modified as a consequence of changing server properties. Let's call vino_server_deinit_io_channels before changing server properties in order to prevent the following errors: https://bugzilla.gnome.org/show_bug.cgi?id=796349 |
Ondrej Holy <oholy@redhat.com> | no | 2018-08-24 | ||
| 0009-Return-empty-string-instead-of-NULL-to-prevent-criti.patch | Return empty string instead of NULL to prevent criticals The code expects that avahi_client_get_host_name_fqdn never return NULL, but it can happen in some cases. Return empty string instead of NULL to prevent the following criticals: GLib-CRITICAL **: 14:29:52.305: g_variant_new_string: assertion 'string != NULL' failed https://bugzilla.gnome.org/show_bug.cgi?id=796349 |
Ondrej Holy <oholy@redhat.com> | no | 2018-08-24 | ||
| 0010-Fix-various-defects-reported-by-covscan.patch | Fix various defects reported by covscan This patch fixes the following important defects reported by covscan: server/libvncserver/main.c:178: leaked_storage: Variable "i" going out of scope leaks the storage it points to. server/libvncserver/rfbserver.c:195: leaked_storage: Variable "cl" going out of scope leaks the storage it points to. server/libvncserver/rfbserver.c:1161: overwrite_var: Overwriting "i" in "i = sraRgnGetIterator(updateRegion)" leaks the storage that "i" server/libvncserver/rfbserver.c:1232: deref_arg: Calling "sraRgnReleaseIterator" dereferences freed pointer "i". server/libvncserver/rfbserver.c:1291: leaked_storage: Variable "i" going out of scope leaks the storage it points to. server/libvncserver/sockets.c:635: leaked_handle: Handle variable "sock" going out of scope leaks the handle. server/libvncserver/sockets.c:635: leaked_handle: Handle variable "sock6" going out of scope leaks the handle. server/libvncserver/sockets.c:639: leaked_handle: Handle variable "sock" going out of scope leaks the handle. server/libvncserver/sockets.c:639: leaked_handle: Handle variable "sock6" going out of scope leaks the handle. server/libvncserver/sockets.c:663: overwrite_var: Overwriting handle "sock" in "sock = NewSocketListenTCP((struct sockaddr *)s4, 16U)" leaks the handle. server/libvncserver/sockets.c:677: overwrite_var: Overwriting handle "sock" in "sock = NewSocketListenTCP((struct sockaddr *)s6, 46U)" leaks the handle. server/libvncserver/sockets.c:691: leaked_handle: Handle variable "sock" going out of scope leaks the handle. server/libvncserver/tableinit24.c:150:7: warning: this 'if' clause does not guard... [-Wmisleading-indentation] server/miniupnp/minissdpc.c:43: buffer_size_warning: Calling strncpy with a maximum size argument of 108 bytes on destination array "addr.sun_path" of size 108 bytes might leave the destination string unterminated. server/miniupnp/miniupnpc.c:405: leaked_handle: Handle variable "sudp" going out of scope leaks the handle. server/smclient/eggsmclient-xsmp.c:1171: missing_va_end: va_end was not called for "ap". |
Ondrej Holy <oholy@redhat.com> | no | 2018-08-28 | ||
| libvncserver_CVE-2014-6053.patch | Check malloc() return value (CVE-2014-6053) Check malloc() return value on client->server ClientCutText message. Client can send up to 2**32-1 bytes of text, and such a large allocation is likely to fail in case of high memory pressure. This would in a server crash (write at address 0). |
no | https://github.com/newsoft/libvncserver/commit/6037a9074d52b1963c97cb28ea1096c7c14cbf28 | |||
| libvncserver_CVE-2018-7225.patch | CVE-2018-7225 | Markus Koschany <apo@debian.org> | no | debian | https://github.com/LibVNC/libvncserver/commit/b0c77391e6bd0a2305bbc9b37a2499af74ddd9ee | 2018-06-05 |
| libvncserver_CVE-2019-15681.patch | [PATCH] rfbserver: don't leak stack memory to the remote Thanks go to Pavel Cheremushkin of Kaspersky for reporting. |
Christian Beier <dontmind@freeshell.org> | no | 2019-08-19 |