# CVE-2012-3022: File upload in n/a

> Remote attackers can execute arbitrary code on client machines via a crafted website exploiting an ActiveX control in Canary Labs TrendLink.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** No
- **Published:** 16 Apr 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gv82-f5xg-v657

## What is CVE-2012-3022?

CVE-2012-3022 is a high-severity vulnerability in n/a, published on 16 Apr 2013. 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 SaveToFile method in a certain ActiveX control in TrendDisplay.dll in Canary Labs TrendLink 9.0.2.27051 and earlier does not properly restrict the creation of files, which allows remote attackers to download an arbitrary program onto a client machine, and execute this program, via a crafted web site.

Weakness: CWE-264

## Which versions are affected by CVE-2012-3022?

It affects 1 product.


Products: Canarylabs Trendlink.

## How do I fix CVE-2012-3022?

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

## Is CVE-2012-3022 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3022 and fix it if it is affected.

What it is: CVE-2012-3022 is a high-severity vulnerability in n/a, published on 16 Apr 2013. 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-2012-3022 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-2012-3022/ (Markdown: https://insights.sbomify.com/CVE-2012-3022/index.md)
```

## Sources

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

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