# CVE-2007-4972: Privilege escalation in n/a

> Local attackers can exploit improper SSDT validation in RegMon to crash the system or escalate privileges via kernel hooks.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:N/A:P`)
- **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:** 19 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q6cj-qmpc-5g2g

## What is CVE-2007-4972?

CVE-2007-4972 is a low-severity vulnerability in n/a, published on 19 Sep 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RegMon 7.04 does not properly validate certain parameters to System Service Descriptor Table (SSDT) function handlers, which allows local users to cause a denial of service (crash) and possibly gain privileges via kernel SSDT hooks to the (1) NtCreateKey and (2) NtOpenKey Windows Native API functions.

Weakness: CWE-264

## Which versions are affected by CVE-2007-4972?

It affects 1 product.


Products: Sysinternals Regmon.

## How do I fix CVE-2007-4972?

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

## Is CVE-2007-4972 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1748](https://insights.sbomify.com/CVE-2004-1748/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4972 and fix it if it is affected.

What it is: CVE-2007-4972 is a low-severity vulnerability in n/a, published on 19 Sep 2007. 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-2007-4972 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-2007-4972/ (Markdown: https://insights.sbomify.com/CVE-2007-4972/index.md)
```

## Sources

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

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