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

> Remote attackers can cause denial of service or potentially execute code via a use-after-free flaw in the Mono runtime when handling DynamicMethod instances.

- **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:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6gxj-qxj4-wm7j

## What is CVE-2011-0991?

CVE-2011-0991 is a medium-severity use after free vulnerability in n/a, published on 13 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to finalizing and then resurrecting a DynamicMethod instance.

Weakness: CWE-399

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

It affects 2 products.


Products: Mono Mono, Novell Moonlight.

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

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

## Is CVE-2011-0991 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4254](https://insights.sbomify.com/CVE-2010-4254/): Code injection in n/a (high 7.5)
- [CVE-2007-5197](https://insights.sbomify.com/CVE-2007-5197/): Memory corruption in n/a (high 7.5)
- [CVE-2010-4159](https://insights.sbomify.com/CVE-2010-4159/): Path traversal in n/a (medium 6.9)
- [CVE-2006-5072](https://insights.sbomify.com/CVE-2006-5072/): Path traversal in n/a (medium 6.2)
- [CVE-2011-0989](https://insights.sbomify.com/CVE-2011-0989/): Memory corruption in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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