Skip to content
Fencer Intel
medium 5.1

CVE-2011-1165 json

Vino, possibly before 3.2, does not properly document that it opens ports in UPnP routers when the "Configure network to automatically acce…

published 2013-03-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1175

cvss
5.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • vino RHEL 6 2.28.1-8.el6_3

red hat advisories RHSA-2013:0169

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-1165 updated cvss 4.6

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

  • Red Hat Enterprise Linux Desktop (v. 6) vino 2.28.1-8.el6_3 Red Hat Enterprise Linux Server (v. 6) vino 2.28.1-8.el6_3 Red Hat Enterprise Linux Workstation (v. 6) vino 2.28.1-8.el6_3
    fixed: vendor fix RHSA-2013:0169
  • Red Hat Enterprise Linux 4 vino Red Hat Enterprise Linux 5 vino
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.27% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • git.gnome.org http://git.gnome.org/browse/vino/commit/?id=410bbf8e284409bdef02322af4d4a3a388419566 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.