# CVE-2008-5660: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in Vinagre when processing crafted URIs or VNC responses.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5660, GHSA-qq3g-2vhj-h4wr

## What is CVE-2008-5660?

CVE-2008-5660 is a medium-severity vulnerability in n/a, published on 17 Dec 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in the vinagre_utils_show_error function (src/vinagre-utils.c) in Vinagre 0.5.x before 0.5.2 and 2.x before 2.24.2 might allow remote attackers to execute arbitrary code via format string specifiers in a crafted URI or VNC server response.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2008-5660?

It affects 1 product.


Products: Gnome Vinagre.

## How do I fix CVE-2008-5660?

Upgrade to a fixed version.

## Is CVE-2008-5660 being exploited?

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

Public exploit code:

- Vinagre < 2.24.2 - 'show_error()' Remote Format String (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5660 and fix it if it is affected.

What it is: CVE-2008-5660 is a medium-severity vulnerability in n/a, published on 17 Dec 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5660 exists.

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-2008-5660/ (Markdown: https://insights.sbomify.com/CVE-2008-5660/index.md)
```

## Sources

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

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