# CVE-2013-5745: Denial of service in n/a

> Remote attackers can cause a denial of service in GNOME Vino via crafted requests during authentication, leading to infinite loops and resource exhaustion.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-5745, GHSA-vjj5-vm4p-gf6m, MGASA-2013-0300, RHSA-2013:1452

## What is CVE-2013-5745?

CVE-2013-5745 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 1 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-5745?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vino` | Red Hat:enterprise_linux:5::client | All versions | 0:2.13.5-10.el5_10 |
| `vino-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.13.5-10.el5_10 |
| `vino` | Red Hat:enterprise_linux:5::server | All versions | 0:2.13.5-10.el5_10 |
| `vino-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.13.5-10.el5_10 |
| `vino` | Red Hat:enterprise_linux:6::client | All versions | 0:2.28.1-9.el6_4 |
| `vino-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.28.1-9.el6_4 |
| `vino` | Red Hat:enterprise_linux:6::server | All versions | 0:2.28.1-9.el6_4 |
| `vino-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.28.1-9.el6_4 |
| `vino` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.28.1-9.el6_4 |
| `vino-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.28.1-9.el6_4 |

Products: Canonical Ubuntu Linux, David King Vino.

## How do I fix CVE-2013-5745?

Apply the vendor's patch.

## Is CVE-2013-5745 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5745 exists.

Public exploit code:

- Vino VNC Server 3.7.3 - Persistent Denial of Service (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5745 and fix it if it is affected.

What it is: CVE-2013-5745 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 1 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5745 exists.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-5745/ (Markdown: https://insights.sbomify.com/CVE-2013-5745/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-5745
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-5745
- OSV: https://osv.dev/vulnerability/CVE-2013-5745

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-5745/
Summaries are generated and may contain mistakes; the official description above is the record.