dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-56333

CRITICAL · 9.4 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 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
Onyxia is a web app that aims at being the glue between multiple open source backend technologies to provide a state of art working environment for data scientists. This critical vulnerability allows authenticated users to remotely execute code within the Onyxia-API, leading to potential consequences such as unauthorized access to other user environments and denial of service attacks. This issue has been patched in api versions 4.2.0, 3.1.1, and 2.8.2. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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 · high confidence

This is an authenticated remote code execution (RCE) vulnerability in the Onyxia-API component. An authenticated user can execute arbitrary code within the API service, potentially gaining unauthorized access to other user environments or causing denial of service.

MitigationUpgrade Onyxia-API to version 4.2.0, 3.1.1, or 2.8.2 (whichever aligns with the current major version). No workarounds exist.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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. Identify Onyxia-API installation
    Search for Onyxia-API in your environment, checking container registries, deployment manifests, or running services. Look for processes or containers named 'onyxia-api' or related services that expose API endpoints on typical ports (default is often 8000 or 8080).
    Affected if Onyxia-API is not found in your environment, then you are not affected.
  2. Determine installed version
    Check the running Onyxia-API service version by querying its /version or /health endpoint, reviewing container image tags, checking your deployment configuration files, or inspecting environment variables such as ONYXIA_API_VERSION.
    Affected if The installed version cannot be determined and the service is present, treat it as potentially vulnerable.
  3. Compare version against fixed releases
    Compare your installed version to the known fixed versions: 4.2.0, 3.1.1, and 2.8.2. If your version starts with 4.x and is below 4.2.0, or starts with 3.x and is below 3.1.1, or starts with 2.x and is below 2.8.2, the installation is vulnerable.
    Affected if The installed version is below any of these thresholds: 4.2.0 for 4.x versions, 3.1.1 for 3.x versions, or 2.8.2 for 2.x versions.
  4. Verify API network exposure
    Review your network policies, firewall rules, or ingress configurations to determine if the Onyxia-API service is accessible from untrusted networks. Check if the API port is exposed to the internet or to non-admin users.
    Affected if The API is exposed to untrusted users or networks, exploitation becomes possible once valid credentials are obtained.
  5. Confirm authentication is required
    Verify that authentication is enabled for the Onyxia-API endpoints. Check if unauthenticated requests are rejected or if there are any endpoints that permit anonymous access. Review your authentication configuration or API gateway settings.
    Affected if Authentication is disabled or bypassed, the RCE can be exploited by any unauthenticated attacker.

Your environment is affected if Onyxia-API is running a version below 4.2.0, 3.1.1, or 2.8.2 (depending on your major version branch), the API is network-accessible to potential attackers, and authentication is enforced but relies on credentials that could be compromised.

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 Onyxia-API to version 4.2.0, 3.1.1, or 2.8.2 (whichever aligns with the current major version). No workarounds exist.

Recommended fix High confidence

api version 4.2.0 (for 4.x), 3.1.1 (for 3.x), or 2.8.2 (for 2.x)

  1. Identify the current version of the Onyxia-API deployment
  2. Determine the appropriate upgrade path based on your current major version (4.x -> 4.2.0, 3.x -> 3.1.1, or 2.x -> 2.8.2)
  3. Upgrade the Onyxia-API to the corresponding fixed version (4.2.0, 3.1.1, or 2.8.2) using your deployment method
  4. Verify the upgrade was successful and the service is running
  5. Test that the code injection vulnerability is no longer exploitable

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56333 — 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-56333 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