CVE-2023-3361 json
S3 credentials included when exporting elyra notebook
published 2023-10-04 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-44028
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
A 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.
Patch / fix
- opendatahub open_data_hub_dashboard 1.28.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-3361 updated cvss 7.5
odh-dashboard: s3 credentials included when exporting elyra notebook
-
Red Hat OpenShift Data Science (RHODS) rhods/odh-dashboard-rhel8affected: no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- n/a odh-dashboard
- Red Hat Red Hat OpenShift Data Science (RHODS)
Classification
References
-
access.redhat.com
/security/cve/CVE-2023-3361
vdb-entry, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2216588
issue-tracking, third-party-advisory
-
github.com
/opendatahub-io/odh-dashboard/issues/1415
issue-tracking
Sources
- CVE List CVE-2023-3361
- NVD CVE-2023-3361
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.