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

> Remote attackers can execute arbitrary code via crafted Bluetooth packets due to improper memory handling in the Windows Bluetooth Stack.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7mwx-v437-3gjj

## What is CVE-2011-1265?

CVE-2011-1265 is a high-severity use after free vulnerability in Microsoft Windows 7, published on 13 Jul 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Bluetooth Stack 2.1 in Microsoft Windows Vista SP1 and SP2 and Windows 7 Gold and SP1 does not prevent access to objects in memory that (1) were not properly initialized or (2) have been deleted, which allows remote attackers to execute arbitrary code via crafted Bluetooth packets, aka "Bluetooth Stack Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 3 products.


Products: Bluetooth Bluetooth Stack, Microsoft Windows 7, Microsoft Windows Vista.

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

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

## Is CVE-2011-1265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1265 is a high-severity use after free vulnerability in Microsoft Windows 7, published on 13 Jul 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1265 in the wild and no public exploit code.

Affected product: Microsoft Windows 7. 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-1265/ (Markdown: https://insights.sbomify.com/CVE-2011-1265/index.md)
```

## Sources

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

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