# CVE-2023-3361: S3 credentials included when exporting elyra notebook

> Exporting pipelines in Elyra leaks S3 credentials in plain text, allowing attackers to access sensitive storage data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-gj4f-3qq5-j78j

## What is CVE-2023-3361?

CVE-2023-3361 is a high-severity vulnerability in Red Hat OpenShift Data Science (RHODS), published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-3361?

It affects 2 products.


Products: Opendatahub Open Data Hub Dashboard, Redhat Openshift Data Science.

## How do I fix CVE-2023-3361?

No fix has been published for CVE-2023-3361 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-3361 being exploited?

There is no known exploitation of CVE-2023-3361 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3361 and fix it if it is affected.

What it is: CVE-2023-3361 is a high-severity vulnerability in Red Hat OpenShift Data Science (RHODS), published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3361 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Data Science (RHODS). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3361/ (Markdown: https://insights.sbomify.com/CVE-2023-3361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3361
- OSV: https://osv.dev/vulnerability/CVE-2023-3361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3361/
Summaries are generated and may contain mistakes; the official description above is the record.