Vulnerability in Vino: External Network Connection Risk

vino Updated 02 Oct 2025

Summary

12/03/2013
N/A
No i
Unrated
Not published

DEBIAN-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 for remote attackers to perform attacks. Affects vino versions 3.22.0-6 – 3.22.0-7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Vino is a remote desktop sharing server for the GNOME desktop environment, allowing users to connect to their desktop remotely. It is designed to facilitate remote access and control, making it easier for users to share their screens or assist others. However, prior to version 2.99.4, Vino had a significant vulnerability that allowed it to connect to external networks, contradicting its intended functionality as stated in the vino-preferences dialog box.

Vulnerability Detail

The vulnerability identified as CVE-2011-1164 in Vino allows the software to connect to external networks, which poses a security risk by enabling remote attackers to exploit this feature for unauthorized access. This issue arises from a flaw in the configuration settings of Vino, which does not restrict connections as expected. The ramifications of this vulnerability could lead to unauthorized control over the user's desktop, potentially resulting in data breaches or other malicious activities.

How To Fix

No fixed version is published for this vulnerability.

To rectify this vulnerability, users should update Vino to the patched version 2.99.4 or later. This can typically be done using the package manager on Debian systems. The command to update Vino is as follows:

sudo apt-get update && sudo apt-get install vino

This will ensure that the latest security patches are applied.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can disable remote desktop sharing in Vino until the package is updated. This can be done by navigating to the Vino preferences and unchecking the option to allow remote connections.

Conclusion

The vulnerability in Vino, identified as CVE-2011-1164, poses a significant risk by allowing external network connections. Users are advised to update to version 2.99.4 or later to mitigate this risk. Until an update can be applied, disabling remote desktop sharing is recommended.

See every vulnerability recorded for vino →

Share this vulnerability

FAQ

CVE-2011-1164 is a vulnerability in Vino that allows it to connect to external networks, potentially enabling unauthorized remote access.

You can check your version of Vino by running the command 'vino --version' in the terminal. If it is below 2.99.4, it is affected.

If you cannot update Vino, it is recommended to disable remote desktop sharing until the update can be applied.

More information can be found in the official CVE database or by visiting the Debian security advisory related to CVE-2011-1164.

Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed about potential risks.

Related vulnerabilities

Recent vulnerabilities recorded for vino.

How To Fix

No fixed version is published for this vulnerability.

To rectify this vulnerability, users should update Vino to the patched version 2.99.4 or later. This can typically be done using the package manager on Debian systems. The command to update Vino is as follows:

sudo apt-get update && sudo apt-get install vino

This will ensure that the latest security patches are applied.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.