dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2019-3889

MEDIUM · 5.4 CVSS v3.1 Published 2019-07-11
Fix available
A fix is available. Upgrade to after 3.11 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 reflected XSS vulnerability exists in authorization flow of OpenShift Container Platform versions: openshift-online-3, openshift-enterprise-3.4 through 3.7 and openshift-enterprise-3.9 through 3.11. An attacker could use this flaw to steal authorization data by getting them to click on a malicious link.

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 · high confidence

A reflected XSS vulnerability exists in the authorization flow of OpenShift Container Platform versions 3.4-3.7 and 3.9-3.11. Attackers can craft malicious URLs containing JavaScript that gets executed in victims' browsers when clicked, enabling theft of authorization data such as session tokens or credentials.

MitigationApply vendor patches for this vulnerability. Until patched, warn users not to click untrusted links and implement Content Security Policy headers as a defense-in-depth measure.

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
Affected:>= 3.4, <= 3.7>= 3.9, <= 3.11= 4.1= 4.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 checks

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

  1. Identify installed OpenShift Container Platform version
    Run 'oc version' or check the OSE version file at /etc/origin/server/version. For OCP 4.x, run 'oc get clusterversion version -o jsonpath='{.spec.clusterID}'' and check the associated versions.
    Affected if The installed version falls within 3.4 to 3.7, 3.9 to 3.11, 4.1, or 4.2.
  2. Confirm the authorization endpoint is exposed
    Check if the OpenShift OAuth server or authorization endpoint is accessible externally or to untrusted users. Review router and load balancer configurations, and check network policies controlling access to port 8443 (or your configured OAuth port).
    Affected if The OAuth/authorization endpoint is accessible to users who could click malicious links.
  3. Review OAuth authorization flow configuration
    Inspect the OAuth configuration with 'oc get oauth cluster -o yaml' and examine the 'tokenConfig' and 'identityProviders' settings. Look for any custom templates or callback URLs that may reflect user input.
    Affected if Custom templates or identity provider configurations that could reflect URL parameters exist.
  4. Check for Content Security Policy headers
    Inspect HTTP responses from the OAuth endpoint using 'curl -I https://<openshift-host>/oauth/authorize' and look for CSP headers. Also check router and load balancer configurations for CSP enforcement.
    Affected if No CSP headers are set, or they do not restrict script execution.
  5. Audit access logs for suspicious URL patterns
    Review access logs from the OAuth server for requests containing '<script>', 'javascript:', or other XSS payload patterns in the authorization flow parameters.
    Affected if Such patterns appear in logs, indicating possible exploitation attempts.

A user is affected if their OpenShift version is 3.4-3.7, 3.9-3.11, 4.1, or 4.2 and the OAuth authorization endpoint is accessible to users who could click untrusted crafted links.

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.

From vendor data
Upgrade available Upgrade to a release after 3.11
Interim mitigation

Apply vendor patches for this vulnerability. Until patched, warn users not to click untrusted links and implement Content Security Policy headers as a defense-in-depth measure.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3889 — 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-2019-3889 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