# CVE-2024-36424: Null dereference in n/a

> Local attackers can cause a system crash (BSOD) in K7 Ultimate Security via a NULL pointer dereference in the kernel driver.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 6 Aug 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-jjrf-959r-8466

## What is CVE-2024-36424?

CVE-2024-36424 is a medium-severity vulnerability in n/a, published on 6 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

K7RKScan.sys in K7 Ultimate Security before 17.0.2019 allows local users to cause a denial of service (BSOD) because of a NULL pointer dereference.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-36424?

It affects 1 product.


Products: K7computing K7 Ultimate Security.

## How do I fix CVE-2024-36424?

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

## Is CVE-2024-36424 being exploited?

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

Public exploit code:

- K7 Ultimate Security < v17.0.2019 "K7RKScan.sys" Null Pointer Dereference PoC  (github_poc): https://github.com/secunnix/CVE-2024-36424
- K7 Ultimate Security K7RKScan.sys 17.0.2019 - Denial Of Service (DoS) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-16896](https://insights.sbomify.com/CVE-2019-16896/): Path traversal in n/a (high 7.8)
- [CVE-2025-67826](https://insights.sbomify.com/CVE-2025-67826/): Privilege escalation in n/a (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36424 and fix it if it is affected.

What it is: CVE-2024-36424 is a medium-severity vulnerability in n/a, published on 6 Aug 2024. 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-2024-36424 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-2024-36424/ (Markdown: https://insights.sbomify.com/CVE-2024-36424/index.md)
```

## Sources

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

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