# CVE-2008-7211: Null dereference in n/a

> Local attackers can gain SYSTEM privileges via a crafted IRP request exploiting a NULL pointer dereference in the CreativeLabs es1371mp.sys audio driver.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v4wc-v886-8pvp

## What is CVE-2008-7211?

CVE-2008-7211 is a medium-severity vulnerability in n/a, published on 11 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CreativeLabs es1371mp.sys 5.1.3612.0 WDM audio driver, as used in Ensoniq PCI 1371 sound cards and when running on Windows Vista, does not create a Functional Device Object (FDO) to prevent user-moade access to the Physical Device Object (PDO), which allows local users to gain SYSTEM privileges via a crafted IRP request that dereferences a NULL FsContext pointer.

## Which versions are affected by CVE-2008-7211?

It affects 1 product.


Products: Soundblaster Ensoniq Pci Es1371 Wdm Driver.

## How do I fix CVE-2008-7211?

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

## Is CVE-2008-7211 being exploited?

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

Public exploit code:

- Creative Ensoniq PCI ES1371 WDM Driver 5.1.3612 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7211 and fix it if it is affected.

What it is: CVE-2008-7211 is a medium-severity vulnerability in n/a, published on 11 Sep 2009. 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-2008-7211 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-2008-7211/ (Markdown: https://insights.sbomify.com/CVE-2008-7211/index.md)
```

## Sources

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

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