# CVE-2011-3488: Use after free in n/a

> Remote attackers can execute arbitrary code by tricking users into opening malformed chart or template files in Equis MetaStock.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/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 Sep 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-p4m5-88fq-rvr6

## What is CVE-2011-3488?

CVE-2011-3488 is a critical use after free vulnerability in n/a, published on 16 Sep 2011. 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

Use-after-free vulnerability in Equis MetaStock 11 and earlier allows remote attackers to execute arbitrary code via a malformed (1) mwc chart, (2) mws chart, (3) mwt template, or (4) mwl layout.

Weakness: CWE-399

## Which versions are affected by CVE-2011-3488?

It affects 1 product.


Products: Equis Metastock.

## How do I fix CVE-2011-3488?

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

## Is CVE-2011-3488 being exploited?

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

Public exploit code:

- Equis MetaStock 11 - Use-After-Free (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3488 and fix it if it is affected.

What it is: CVE-2011-3488 is a critical use after free vulnerability in n/a, published on 16 Sep 2011. 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-2011-3488 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-2011-3488/ (Markdown: https://insights.sbomify.com/CVE-2011-3488/index.md)
```

## Sources

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

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