Phishing via protocol-agnostic CORS origin matching
Published Apr 24, 2020 · Updated Aug 4, 2024
CORS origin validation in Red Hat OpenShift Ansible 3.11 allows man-in-the-middle attackers to conduct phishing attacks. The installer writes a protocol-agnostic regular expression into the OpenShift master corsAllowedOrigins configuration, allowing an origin with an unintended URL scheme to satisfy the allowlist. Exploitation requires interception of a user's browser connection to the OpenShift console; the accepted cross-origin context exposes confidential data through phishing.
Summary
What happened
CORS origin validation in Red Hat OpenShift Ansible 3.11 allows man-in-the-middle attackers to conduct phishing attacks. The installer writes a protocol-agnostic regular expression into the OpenShift master corsAllowedOrigins configuration, allowing an origin with an unintended URL scheme to satisfy the allowlist. Exploitation requires interception of a user's browser connection to the OpenShift console; the accepted cross-origin context exposes confidential data through phishing.
The record
- CVE
- CVE-2020-1741
- Published
- Apr 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- OpenShift Ansible
- Classifications
- CWE-185, CWE-697, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=openshift-ansible-3.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo