Back

MEDIUM

vino-preferences does not warn about UPnP especially with no password and no confirmation.

Published Mar 12, 2013

Description

Vino, possibly before 3.2, does not properly document that it opens ports in UPnP routers when the "Configure network to automatically accept connections" setting is enabled, which might make it easier for remote attackers to perform further attacks.

Affected products

Remediation

Red Hat statement

This issue did not affect the version of vino as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for Universal Plug and Play (UPnP). A future update in Red Hat Enterprise Linux 6 may address this flaw. To mitigate this issue, users should ensure that confirmation is requested on each inbound connection attempt, that a password is required to connect, and that automatic network configuration is disabled. This will prevent vino from using UPnP to allow access to the VNC port, and will ensure that any connections require a password and that the user is notified on any connection attempts.

Weaknesses (0)

No CWE recorded.

References (9)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner redhat
Published Mar 12, 2013
Updated Aug 6, 2024
Reserved Mar 3, 2011
NVD
Status Modified
Modified Jun 16, 2026
Red Hat
Severity Low
Public date Sep 8, 2009
ENISA EUVD
Assigner redhat
Published Mar 12, 2013
Updated Aug 6, 2024
Exploited since n/a
EUVD-2011-1175