dbcve.org
Single Sign OnApplication · Redhat

CVE-2022-4039

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A flaw was found in Red Hat Single Sign-On for OpenShift container images, which are configured with an unsecured management interface enabled. This flaw allows an attacker to use this interface to deploy malicious code and access and modify potentially sensitive information in the app server configuration.

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 confidence

Red Hat Single Sign-On for OpenShift container images are shipped with an unprotected management interface enabled. An unauthenticated attacker can access this interface to inject malicious code into the app server and read or modify sensitive configuration data including credentials and security settings.

MitigationDisable or restrict the unsecured management interface in the container image configuration, apply proper authentication, and rebuild/redeploy the affected RH-SSO containers with hardened settings.

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
Single Sign OnApplication
Affected:= 7.0
Openshift Container PlatformApplication
Affected:= 4.9= 4.10
Openshift Container Platform For Ibm ZApplication
Affected:= 4.9= 4.10
Openshift Container Platform For LinuxoneApplication
Affected:= 4.9= 4.10
Openshift Container Platform For PowerApplication
Affected:= 4.9= 4.10

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify RH-SSO container deployments
    Run 'oc get pods -A | grep -i sso' or 'kubectl get pods -A | grep -i sso' to list any Red Hat Single Sign-On pods running in the cluster
    Affected if RH-SSO pods are found running in the namespace
  2. Verify RH-SSO version
    Check the container image version using 'oc get pods -o jsonpath="{.items[*].spec.containers[*].image}" -l app=sso" or inspect the deployment configuration for the exact RH-SSO version tag
    Affected if The RH-SSO version is 7.0
  3. Verify OpenShift Container Platform version
    Run 'oc version' or check the cluster version with 'oc get clusterversion' to determine the OCP version
    Affected if The OpenShift version is 4.9 or 4.10
  4. Detect exposed management interface
    Check for listening ports on the RH-SSO pod using 'oc exec <sso-pod> -- netstat -tlnp' or check the service/ingress configuration with 'oc get svc -A' and 'oc get ingress -A' for any management endpoints exposed externally
    Affected if Port 9990 (management) or other management ports are exposed externally without authentication requirements
  5. Confirm management interface access control
    Inspect the standalone.xml or the Elytron security configuration inside the container for the management interface definition, or test unauthenticated access to the management endpoint via curl/curl -k http://<sso-pod>:9990/management
    Affected if The management interface allows unauthenticated access or has no authentication layer configured

You are affected if RH-SSO version 7.0 is running on OpenShift 4.9 or 4.10 with the management interface exposed and accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or restrict the unsecured management interface in the container image configuration, apply proper authentication, and rebuild/redeploy the affected RH-SSO containers with hardened settings.

Recommended fix Moderate confidence

OpenShift Container Platform 4.11 or later (which includes patched Single Sign-On 7.x container images)

  1. Update OpenShift Container Platform to version 4.11 or later, which contains the patched Single Sign-On container images
  2. If unable to upgrade OpenShift immediately, ensure the management interface is disabled by setting the appropriate environment variables or configuration in the SSO deployment
  3. For Red Hat Single Sign-On for OpenShift, verify that the management interface is not exposed on insecure ports (typically ports 8080/8443) and is only accessible via secured channels
  4. Review container network policies to restrict access to management interfaces
  5. After applying updates, verify the management interface is no longer accessible without authentication
Caveat Upgrading OpenShift may require cluster downtime and compatibility checks with existing workloads; ensure backup and test migration path before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Single Sign On Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4039 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4039 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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