dbcve.org
Openshift Data ScienceApplication · Redhat

CVE-2023-0923

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-15
Fix available
A fix is available. Upgrade to 1.22.1-3 or later.
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
A flaw was found in the Kubernetes service for notebooks in RHODS, where it does not prevent pods from other namespaces and applications from making requests to the Jupyter API. This flaw can lead to file content exposure and other issues.

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

A flaw in the Kubernetes notebook service in RHODS (Red Hat OpenShift Data Science) fails to enforce proper namespace isolation, allowing pods and applications from other namespaces to make unauthorized requests to the Jupyter API. This cross-namespace access vulnerability enables attackers to access file contents and potentially execute arbitrary code within notebook contexts.

MitigationImplement Kubernetes NetworkPolicies and/or RBAC controls to restrict Jupyter API access to only authorized namespaces and service accounts within the OpenShift cluster.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Data ScienceApplication
Affected:>= 1.22, < 1.22.1-3

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 RHODS installation and version
    Run 'oc get subscription rhoai -n redhat-ods-operator -o jsonpath={.status.currentCSV}' or check the operator namespace for the installed version. Also check 'oc get pods -n redhat-ods-operator' for the rhods-operator version tag.
    Affected if The installed version is 1.22 or later but earlier than 1.22.1-3 (the version string matches 1.22.x where x is 0-2, or falls between 1.22 and 1.22.1-3).
  2. Confirm Jupyter API service is deployed
    Run 'oc get svc jupyterhub -n redhat-ods-applications' or check for notebook-controller pods in the redhat-ods-applications namespace.
    Affected if The JupyterHub or notebook service exists in the 'redhat-ods-applications' namespace, indicating the vulnerable component is present.
  3. Verify namespace isolation configuration
    Check for existing Kubernetes NetworkPolicies in the redhat-ods-applications namespace: 'oc get networkpolicy -n redhat-ods-applications'. Also verify service role bindings: 'oc get rolebinding -n redhat-ods-applications | grep -i jupyter'.
    Affected if No NetworkPolicy exists to restrict Jupyter API access to specific namespaces, or overly permissive RBAC bindings allow cross-namespace access.

A user is affected if Red Hat OpenShift Data Science is installed with a version in the range 1.22 to 1.22.1-3 (exclusive of 1.22.1-3) and the Jupyter API service is exposed without namespace isolation controls.

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
Upgrade available Upgrade to 1.22.1-3 or later
Fixed in 1.22.1-3
Interim mitigation

Implement Kubernetes NetworkPolicies and/or RBAC controls to restrict Jupyter API access to only authorized namespaces and service accounts within the OpenShift cluster.

Recommended fix High confidence

1.22.1-3

  1. Identify the current version of OpenShift Data Science by checking the RHODS operator version in the OpenShift console or via oc CLI
  2. Review the OpenShift Data Science upgrade documentation at access.redhat.com for pre-upgrade requirements
  3. Create a backup of any critical data and configurations
  4. Perform the upgrade to version 1.22.1-3 or later following the documented upgrade procedure
  5. Verify the Jupyter API authorization controls are functioning correctly post-upgrade by testing cross-namespace access restrictions

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

Fix this in Openshift Data Science Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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