# CVE-2024-0581: Uncontrolled Resource Consumption vulnerability on Sandsprite scdbg

> An attacker can cause the Scdbg application to shut down by sending a specially crafted shellcode payload, potentially aiding malware evasion.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-h483-rc58-6r6g

## What is CVE-2024-0581?

CVE-2024-0581 is a medium-severity denial of service vulnerability in Sandsprite Scdbg, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Uncontrolled Resource Consumption vulnerability has been found on Sandsprite Scdbg.exe, affecting version 1.0. This vulnerability allows an attacker to send a specially crafted shellcode payload to the '/foff' parameter and cause an application shutdown. A malware program could use this shellcode sequence to shut down the application and evade the scan.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Sandsprite Scdbg.

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

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

## Is CVE-2024-0581 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0581 is a medium-severity denial of service vulnerability in Sandsprite Scdbg, published on 16 Jan 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-0581 in the wild and no public exploit code.

Affected product: Sandsprite Scdbg. 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-0581/ (Markdown: https://insights.sbomify.com/CVE-2024-0581/index.md)
```

## Sources

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

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