# CVE-2024-4369: Cluster-image-registry-operator: exposes a secret via env variable in pod definition on azure

> Attackers with pod read permissions in Azure environments can expose the Azure client secret, enabling unauthorized actions as the registry operator.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2024
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-cc73-99rj-c7fh

## What is CVE-2024-4369?

CVE-2024-4369 is a medium-severity vulnerability in Red Hat OpenShift Container Platform 4.14, published on 30 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An information disclosure flaw was found in OpenShift's internal image registry operator. The AZURE_CLIENT_SECRET can be exposed through an environment variable defined in the pod definition, but is limited to Azure environments. An attacker controlling an account that has high enough permissions to obtain pod information from the openshift-image-registry namespace could use this obtained client secret to perform actions as the registry operator's Azure service account.

Weakness: CWE-526 (Cleartext Storage of Sensitive Information in an Environment Variable)

## Which versions are affected by CVE-2024-4369?


## How do I fix CVE-2024-4369?

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

## Is CVE-2024-4369 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4369 and fix it if it is affected.

What it is: CVE-2024-4369 is a medium-severity vulnerability in Red Hat OpenShift Container Platform 4.14, published on 30 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4369 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Container Platform 4.14. 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-2024-4369/ (Markdown: https://insights.sbomify.com/CVE-2024-4369/index.md)
```

## Sources

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

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