Openshift Container PlatformApplication · Redhat
CVE-2022-4145
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA content spoofing flaw was found in OpenShift's OAuth endpoint. This flaw allows a remote, unauthenticated attacker to inject text into a webpage, enabling the obfuscation of a phishing operation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA content spoofing vulnerability in OpenShift's OAuth endpoint allows remote, unauthenticated attackers to inject arbitrary text into web pages rendered by the OAuth service, enabling phishing campaign obfuscation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift Container PlatformApplication
= 4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OpenShift versionRun 'oc get clusterversion' or check /etc/os-release for OpenShift version metadataAffected if version equals 4.0 exactly (the only affected version listed)
-
Verify OAuth endpoint is exposedCheck route or ingress configuration for oauth endpoint: 'oc get routes -n openshift-authentication' or inspect the OAuth server deploymentAffected if OAuth endpoint is externally accessible without additional network segmentation
-
Inspect OAuth server logs for injection attemptsQuery OAuth pod logs: 'oc logs -n openshift-authentication -l app=oauth-openshift' and search for unexpected HTML/script patterns in request parametersAffected if Logs contain malformed requests with arbitrary text in OAuth parameters that bypass validation
-
Examine OAuth login page source for unexpected contentAccess the OAuth login page directly and view page source, checking for any injected text not originating from known OAuth templatesAffected if OAuth login or consent pages display text that is not defined in OAuth configuration or templates
-
Review OAuth configuration for validation settingsCheck OAuth cluster config: 'oc get oauth cluster -o yaml' and inspect token endpoint configurations for custom templates or validation rulesAffected if OAuth configuration contains custom templates or validation settings that may allow input injection
Environment is affected if running OpenShift Container Platform version 4.0 and the OAuth endpoint is accessible to remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-released patch or upgrade to a fixed OpenShift version that addresses the OAuth endpoint input validation flaw; review OAuth endpoint configurations for unexpected content injection points.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4145 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data