# CVE-2024-0788: SUPERAntiSpyware Pro X v10.0.1260 - Kernel-level API parameters manipulation

> Attackers can cause a denial of service in SUPERAntiSpyware Pro X by manipulating kernel-level API parameters via a specific IOCTL code.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 29 Jan 2024
- **Updated:** 20 May 2025
- **Also known as:** GHSA-rrr4-rqcr-8jmq

## What is CVE-2024-0788?

CVE-2024-0788 is a medium-severity vulnerability in SUPERAntiSpyware Pro X, published on 29 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SUPERAntiSpyware Pro X v10.0.1260 is vulnerable to kernel-level API parameters manipulation and Denial of Service vulnerabilities by triggering the 0x9C402140 IOCTL code of the saskutil64.sys driver.

Weakness: CWE-96 (Improper Neutralization of Directives in Statically Saved Code)

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

It affects 1 product.


Products: Realdefen Superantispyware.

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

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

## Is CVE-2024-0788 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0788 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0788 is a medium-severity vulnerability in SUPERAntiSpyware Pro X, published on 29 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0788 exists.

Affected product: SUPERAntiSpyware Pro X. 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-0788/ (Markdown: https://insights.sbomify.com/CVE-2024-0788/index.md)
```

## Sources

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

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