# CVE-2018-7249: Use after free in n/a

> An unprivileged attacker can exploit a race condition in the secdrv.sys driver to achieve arbitrary code execution in the kernel.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 26 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9357-692c-cj9m

## What is CVE-2018-7249?

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

### Official description

An issue was discovered in secdrv.sys as shipped in Microsoft Windows Vista, Windows 7, Windows 8, and Windows 8.1 before KB3086255, and as shipped in Macrovision SafeDisc. Two carefully timed calls to IOCTL 0xCA002813 can cause a race condition that leads to a use-after-free. When exploited, an unprivileged attacker can run arbitrary code in the kernel.

Weakness: CWE-416 (Use After Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2018-7249?

It affects 5 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Vista, Tivo Safedisc.

## How do I fix CVE-2018-7249?

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

## Is CVE-2018-7249 being exploited?

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

Public exploit code:

- A PoC for CVE-2018-7249 (github_poc): https://github.com/alonhr/NotSecDrv

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7249 and fix it if it is affected.

What it is: CVE-2018-7249 is a high-severity use after free vulnerability in Microsoft Windows 7, published on 26 Feb 2018. 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-2018-7249 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-2018-7249/ (Markdown: https://insights.sbomify.com/CVE-2018-7249/index.md)
```

## Sources

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

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