# CVE-2024-11217: Oauth-server-container: oauth-server-container logs client secret in debug level

> Attackers with access to debug logs can obtain OAuth2 client secrets when debug logging is enabled in Red Hat OpenShift.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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:** 15 Nov 2024
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-c363-2f5p-c4cv

## What is CVE-2024-11217?

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

### Official description

A vulnerability was found in the OAuth-server. OAuth-server logs the OAuth2 client secret when the logLevel is Debug higher for OIDC/GitHub/GitLab/Google IDPs login options.

Weakness: CWE-1295 (Debug Messages Revealing Unnecessary Information)

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


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

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

## Is CVE-2024-11217 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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