Openshift Data ScienceApplication · Redhat
CVE-2023-3361
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 · uneditedA flaw was found in Red Hat OpenShift Data Science. When exporting a pipeline from the Elyra notebook pipeline editor as Python DSL or YAML, it reads S3 credentials from the cluster (ds pipeline server) and saves them in plain text in the generated output instead of an ID for a Kubernetes secret.
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 confidenceWhen exporting pipelines from the Elyra notebook pipeline editor in Red Hat OpenShift Data Science as Python DSL or YAML, the application reads S3 credentials from the cluster and writes them in plain text to the exported files, rather than referencing a Kubernetes secret ID. This exposes sensitive credentials to anyone with access to the exported pipeline files.
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
all versions< 1.28.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if OpenShift Data Science or Open Data Hub Dashboard is deployedCheck your cluster for the presence of the OpenShift Data Science operator or Opendatahub operator. For OpenShift, look for the rhods-operator or opendatahub-operator in the openshift-operators namespace.Affected if Either product is installed, as both include the vulnerable Elyra component.
-
Check for Elyra notebook pipeline usageLook for Elyra pipeline definitions in your namespace. Search for files with .py or .ipynb extensions that contain Elyra pipeline components, or check for pipeline Custom Resources.Affected if Elyra pipelines are being created or used in the environment.
-
Locate exported pipeline filesSearch for .py and .yaml files in user home directories, project directories, and any shared storage. Look for files containing 'elyra' or pipeline-related content, especially in locations where pipeline exports are typically saved.Affected if Exported pipeline files exist, particularly those exported as Python DSL or YAML format.
-
Inspect exported files for plain text S3 credentialsSearch exported pipeline files for AWS credentials in plain text. Look for patterns like 'AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY', 's3_endpoint', or base64-encoded credentials that are not referenced as Kubernetes secret IDs.Affected if The exported pipeline files contain S3 credentials written in plain text rather than as secret references.
A user is affected if they have OpenShift Data Science or Open Data Hub Dashboard (prior to 1.28.1) and have exported Elyra pipelines that contain S3 credentials stored as plain text in the exported files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.28.1
Await the vendor patch from Red Hat; in the interim, avoid exporting pipelines containing S3 credentials, audit for any previously exported files containing exposed credentials, and rotate any compromised credentials immediately.
Open Data Hub Dashboard >= 1.28.1
- For Open Data Hub Dashboard users: Upgrade to version 1.28.1 or later to resolve the credential exposure vulnerability
- For OpenShift Data Science: As all versions are affected and no fix version is specified in the available documentation, contact Red Hat support for specific guidance or consider migrating to Open Data Hub Dashboard 1.28.1+ which contains the fix
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
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3361 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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