OpenShift Controller Manager Improper Privilege Management

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L · score source

EPSS

• CVE-2024-45496: 1.02% estimated exploitation activity in the next 30 days; percentile 63.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A flaw was found in OpenShift. This issue occurs due to the misuse of elevated privileges in the OpenShift Container Platform's build process. During the build initialization step, the git-clone container is run with a privileged security context, allowing unrestricted access to the node. An attacker with developer-level access can provide a crafted .gitconfig file containing commands executed during the cloning process, leading to arbitrary command execution on the worker node. An attacker running code in a privileged container could escalate their permissions on the node running the container.

Published by the source

17 Sep 2024, 00:31 UTC

Last modified by the source

9 Jan 2025, 09:31 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j8gh-87rx-c7w9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-45496

Advisory: OpenShift Controller Manager Improper Privilege Management
IDs: CVE-2024-45496, GHSA-j8gh-87rx-c7w9
Record: https://patchnext.com/advisories/cve-2024-45496 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openshift/openshift-controller-manager 0.0.0-alpha.0.0.20240911. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openshift/openshift-controller-manager: affected < 0.0.0-alpha.0.0.20240911; fixed in 0.0.0-alpha.0.0.20240911

## Suggested inspection (read-only)
- Go github.com/openshift/openshift-controller-manager: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openshift/openshift-controller-manager.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8gh-87rx-c7w9 (GitHub-reviewed advisory GHSA-j8gh-87rx-c7w9 lists affected ranges: Go github.com/openshift/openshift-controller-manager >=0 <0.0.0-alpha.0.0.20240911)

Commands are suggestions: review each one before running it.