Skip to content
Noroxi
CVE-2013-5745· NVD / CVE Program· CNA mitre

The 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 d

The 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 disabled, does not properly clear client data when an error causes the connection to close during authentication, which allows remote attackers to cause a denial of service (infinite loop, CPU and disk consumption) via multiple crafted requests during authentication.

HighCVSS 7.1 · v2.0—Proof of concept Fix available
Published
Oct 1, 2013
Updated
Jun 16, 2026
EPSS
8.7% · 95th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 8.7%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
david kingvino
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux12.04
  • canonical ubuntu linux12.10
  • canonical ubuntu linux13.04
  • david king vinoup to 3.7.3 inclusive
  • david king vino0.12
  • david king vino0.14
  • 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
  • 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12vinobefore 3.10.1-13.10.1-1
Red Hat:enterprise_linux:5::clientvinobefore 0:2.13.5-10.el5_100:2.13.5-10.el5_10
Red Hat:enterprise_linux:5::clientvino-debuginfobefore 0:2.13.5-10.el5_100:2.13.5-10.el5_10
Red Hat:enterprise_linux:6::clientvinobefore 0:2.28.1-9.el6_40:2.28.1-9.el6_4
Red Hat:enterprise_linux:6::clientvino-debuginfobefore 0:2.28.1-9.el6_40:2.28.1-9.el6_4

Other highest-scoring records for the same primary product.

  • CVE-2011-1165Vino, possibly before 3.2, does not properly document that it opens ports in UPnP routers when the "Configure network to automatically accep
    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
  • CVE-2011-1164Vino before 2.99.4 can connect external networks contrary to the statement in the vino-preferences dialog box, which might make it easier fo
    18Monitor
  • CVE-2011-0904The 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, 3.0
    15Monitor
  • CVE-2011-0905The 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, 3.0
    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 / packageFixed versionSource
debian:vino3.10.1-1 · Debian:12Package registry (OSV)
red hat:vino0:2.13.5-10.el5_10 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:vino-debuginfo0:2.13.5-10.el5_10 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrydos2013-09-17

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.

  1. First PoC-15 d
  2. Published
  3. TodayOct 10, 2026+4757 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records