# CVE-2010-2713: Command injection in n/a

> Remote attackers can execute arbitrary commands or read sensitive data via malicious window title escape sequences in the VTE library used by gnome-terminal.

- **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:** 5 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2713, GHSA-h3vh-54q4-255x

## What is CVE-2010-2713?

CVE-2010-2713 is a medium-severity command injection vulnerability in n/a, published on 5 Aug 2010. 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

The vte_sequence_handler_window_manipulation function in vteseq.c in libvte (aka libvte9) in VTE 0.25.1 and earlier, as used in gnome-terminal, does not properly handle escape sequences, which allows remote attackers to execute arbitrary commands or obtain potentially sensitive information via a (1) window title or (2) icon title sequence.  NOTE: this issue exists because of a CVE-2003-0070 regression.

## Which versions are affected by CVE-2010-2713?

It affects 1 product.


Products: Nalin Dahyabhai Vte.

## How do I fix CVE-2010-2713?

Upgrade to a fixed version.

## Is CVE-2010-2713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2738](https://insights.sbomify.com/CVE-2012-2738/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2713 and fix it if it is affected.

What it is: CVE-2010-2713 is a medium-severity command injection vulnerability in n/a, published on 5 Aug 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-2713 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-2010-2713/ (Markdown: https://insights.sbomify.com/CVE-2010-2713/index.md)
```

## Sources

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

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