CVE-2011-1164 json
Vino before 2.99.4 can connect external networks contrary to the statement in the vino-preferences dialog box, which might make it easier f…
published 2013-03-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1174
- cvss
- 4.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Vino before 2.99.4 can connect external networks contrary to the statement in the vino-preferences dialog box, which might make it easier for remote attackers to perform attacks.
Patch / fix
- vino RHEL 6 2.28.1-8.el6_3
red hat advisories RHSA-2013:0169
- vino openSUSE Tumbleweed 3.22.0-1.1
opensuse advisories openSUSE-SU-2024:10047-1
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-1164 updated cvss 4.6
vino: vino-preferences incorrectly indicates that computer is only reachable over local network
-
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_3fixed: vendor fix RHSA-2013:0169
-
Red Hat Enterprise Linux 4 vino Red Hat Enterprise Linux 5 vinonot 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
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-16 Configuration
References
Sources
- CVE List CVE-2011-1164
- NVD CVE-2011-1164
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.