# CVE-2024-56330: Session VNC may be accessed by other sessions on the same host in stardust

> Attackers can access other containers' agents due to enabled inter-container communication, compromising isolation and data confidentiality.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2024
- **Updated:** 24 Dec 2024

## What is CVE-2024-56330?

CVE-2024-56330 is a critical missing authorization vulnerability in spaceness stardust, published on 20 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stardust is a platform for streaming isolated desktop containers. With this exploit, inter container communication (ICC) is not disabled. This would allow users within a container to access another containers agent, therefore compromising access.The problem has been patched in any Stardust build past 12/20/24. Users are advised to upgrade. Users may also manually disable ICC if they are unable to upgrade.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-56330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-56330 is a critical missing authorization vulnerability in spaceness stardust, published on 20 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-56330 in the wild and no public exploit code.

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

## Sources

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

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