dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-56330

CRITICAL · 9.3 CVSS v4.0 Published 2024-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stardust, a platform for streaming isolated desktop containers, has a vulnerability where inter-container communication (ICC) is not disabled by default. This allows malicious or compromised users within one container to access another container's agent, breaking the isolation boundary and enabling cross-container compromise.

MitigationUpgrade to any Stardust build released after 12/20/24 which contains the patch, or manually disable inter-container communication (ICC) as a workaround if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Stardust installation and version
    Locate the Stardust installation directory and check the version file or binary metadata. Common locations include /opt/stardust, /usr/local/stardust, or check via the stardust --version command if available in PATH.
    Affected if The installed version predates the 12/20/24 security update (any version released before the patch date).
  2. Locate ICC configuration settings
    Search for configuration files in Stardust's default config directory. Look for files named stardust.conf, config.json, settings.yaml, or similar that contain network or container isolation settings.
    Affected if A configuration option for inter-container communication (ICC) exists and is set to enabled, true, or 1, or the setting is absent (default behavior uses ICC).
  3. Check container runtime or orchestrator ICC settings
    If Stardust uses an underlying container runtime (Docker, containerd), check the daemon.json or equivalent for theicc= string setting. Look for bridge network configurations or container isolation flags.
    Affected if The container runtime is configured with ICC enabled (icc=true in bridge network settings) or no explicit ICC restriction is defined.
  4. Verify default network isolation
    Inspect the default network profile or container network namespace settings. Check if containers are placed on an isolated network by default or share a network namespace.
    Affected if Containers are placed on a shared network bridge by default without explicit isolation boundaries.

A user is affected if Stardust is running a pre-12/20/24 build with ICC enabled by default, allowing containers to communicate across isolation boundaries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to any Stardust build released after 12/20/24 which contains the patch, or manually disable inter-container communication (ICC) as a workaround if upgrading is not immediately feasible.

Recommended fix Moderate confidence

Any Stardust build released after 12/20/24

  1. Upgrade to any Stardust build released after December 20, 2024, which contains the security patch
  2. Verify the upgrade was successful by confirming the ICC vulnerability is addressed
  3. If unable to upgrade, manually disable inter-container communication (ICC) in the Stardust configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56330 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data