# CVE-2024-42481: Complete crash of host system due to calculateDirectorySize in skyportd

> Attackers can crash the host system by creating excessive files and folders, causing resource exhaustion in the Skyport Daemon.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 13 Aug 2024

## What is CVE-2024-42481?

CVE-2024-42481 is a high-severity denial of service vulnerability in skyportlabs skyportd, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Skyport Daemon (skyportd) is the daemon for the Skyport Panel. By making thousands of folders & files (easy due to skyport's lack of rate limiting on createFolder. createFile), skyportd in a lot of cases will cause 100% CPU usage and an OOM, probably crashing the system. This is fixed in 0.2.2.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Skyport Skyportd.

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

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

## Is CVE-2024-42481 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42481 is a high-severity denial of service vulnerability in skyportlabs skyportd, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42481 exists.

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

## Sources

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

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