# CVE-2019-17414: Denial of service in n/a

> Remote attackers can crash the Vino daemon by sending a long URL, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-37054, AZL-7399, GHSA-x4q7-x73p-9v2w

## What is CVE-2019-17414?

CVE-2019-17414 is a high-severity denial of service vulnerability in n/a, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tinylcy Vino through 2017-12-15 allows remote attackers to cause a denial of service ("vn_get_string error: Resource temporarily unavailable" error and daemon crash) via a long URL.

## Which versions are affected by CVE-2019-17414?

It affects 1 product.


Products: Vino Project Vino.

## How do I fix CVE-2019-17414?

No fix has been published for CVE-2019-17414 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-17414 being exploited?

There is no known exploitation of CVE-2019-17414 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17414 and fix it if it is affected.

What it is: CVE-2019-17414 is a high-severity denial of service vulnerability in n/a, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17414 in the wild and no public exploit code.

Affected product: n/a. 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-2019-17414/ (Markdown: https://insights.sbomify.com/CVE-2019-17414/index.md)
```

## Sources

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

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