Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability if they are running a version prior to 2.35.0. An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token. Version 2.35.0 has introduced a fix for this issue. Users are advised to upgrade. There are no known workarounds for this issue.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Dex | Linuxfoundation | * | 2.35.0 (excluding) |
| Red Hat Advanced Cluster Security 4.3 | RedHat | advanced-cluster-security/rhacs-central-db-rhel8:4.3.1-4 | * |
| Red Hat Advanced Cluster Security 4.3 | RedHat | advanced-cluster-security/rhacs-main-rhel8:4.3.1-9 | * |
| Red Hat Advanced Cluster Security 4.3 | RedHat | advanced-cluster-security/rhacs-rhel8-operator:4.3.1-3 | * |
| Red Hat Advanced Cluster Security 4.3 | RedHat | advanced-cluster-security/rhacs-roxctl-rhel8:4.3.1-3 | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.