CVE-2011-1164: Vino before 2.99.4 can connect external networks contrary to the statement in the vino-preferences dialog box, which might make it easier…
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76.5% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: vino (openSUSE:Tumbleweed) 3.22.0-1.1; vino (Red Hat:enterprise_linux:6::client) 0:2.28.1-8.el6_3; vino-debuginfo (Red Hat:enterprise_linux:6::client) 0:2.28.1-8.el6_3.
Low priority for now. Upgrade to vino (openSUSE:Tumbleweed) 3.22.0-1.1; vino (Red Hat:enterprise_linux:6::client) 0:2.28.1-8.el6_3; vino-debuginfo (Red Hat:enterprise_linux:6::client) 0:2.28.1-8.el6_3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 12, 2013
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 76th percentile
- CWE
- CWE-16
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| david king | vino | cpe:2.3:a:david_king:vino |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- david king vinoup to 2.99.4 inclusive
- david king vino2.10
- david king vino2.11
- david king vino2.11.1
- david king vino2.11.1.1
- david king vino2.11.1.2
- david king vino2.11.90
- david king vino2.11.92
+12 more rows
- david king vino2.12
- david king vino2.13
- david king vino2.13.5
- david king vino2.14
- david king vino2.15
- david king vino2.16
- david king vino2.17
- david king vino2.17.2
- david king vino2.17.4
- david king vino2.17.5
- david king vino2.17.92
- david king vino2.18
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | vino | from 0 | — |
| openSUSE:Tumbleweed | vino | before 3.22.0-1.1 | 3.22.0-1.1 |
| Red Hat:enterprise_linux:6::client | vino | before 0:2.28.1-8.el6_3 | 0:2.28.1-8.el6_3 |
| Red Hat:enterprise_linux:6::client | vino-debuginfo | before 0:2.28.1-8.el6_3 | 0:2.28.1-8.el6_3 |
Same product
david king: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-5745The vino_server_client_data_pending function in vino-server.c in GNOME Vino 2.26.1, 2.32.1, 3.7.3, and earlier, and 3.8 when encryption is…31Monitor
- CVE-2011-1165Vino, possibly before 3.2, does not properly document that it opens ports in UPnP routers when the "Configure network to automatically…21Monitor
- CVE-2012-4429Vino 2.28, 2.32, 3.4.2, and earlier allows remote attackers to read clipboard activity by listening on TCP port 5900.21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-0904May 10, 2011 · The rfbSendFramebufferUpdate function in server/libvncserver/rfbserver.c in vino-server in Vino 2.x before 2.28.3, 2.32.x before 2.32.2…15Monitor
- ← EarlierCVE-2011-0905May 10, 2011 · The rfbSendFramebufferUpdate function in server/libvncserver/rfbserver.c in vino-server in Vino 2.x before 2.28.3, 2.32.x before 2.32.2…14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:vino | 3.22.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:vino | 0:2.28.1-8.el6_3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:vino-debuginfo | 0:2.28.1-8.el6_3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-16 · ConfigurationCVSS vector
AV:N/AC:H/Au:S/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.