BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-39222High confidence

OAuth authorization code exposure in Dex

dexidp · dex

Official source article: GitHub GHSA-VH7G-P26C-J2CW ↗. Check the applicable product and release in the original source.

9.3CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 1.58% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs dexidp dex and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-39222 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitydexidp: gaining access to applications accepting that token
12 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • advanced-cluster-security/rhacs-central-db-rhel8@sha256:2e1f7f206a43b16b9eec84a9138d054a1f8c95c9b620d05160ac32bce119e78b_s390x as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-central-db-rhel8@sha256:a5dbf5803835c61387dac05a01a44486a2308a0e9f9f929e88b6a9b3769f8f60_ppc64le as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-central-db-rhel8@sha256:dfd07bd22ae9ff4a14b06009262650b4eedca84551aa02e0c4ae5e14460c2ed5_amd64 as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-main-rhel8@sha256:5ecf3c2aca847d8df0830ab698fe0e4b1a0216f04495d7e3b6a03440c5359d5a_s390x as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-main-rhel8@sha256:93d6e895f55d2f60c8bf5b10031cc9c025e86f480a7b00cf00dbb54fe4080728_ppc64le as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-main-rhel8@sha256:d25ed99610b530ed8c0b6ba937a6c0822e72ae61022f57c26f0cc775fabf6a21_amd64 as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-rhel8-operator@sha256:0c0638f9f612b93671e798881cdc1205741db4fa08086afa0e3cf57710975586_ppc64le as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-rhel8-operator@sha256:9869d3e2b2d08232aab2f3af99467758b4b95e7d4f72fed9ac6bdd29eb7da81d_s390x as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-rhel8-operator@sha256:acf7dabe654ffee7d6e944f810e6ab19d62ae21e5a96499d1b3898cc56d5da91_amd64 as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-roxctl-rhel8@sha256:63817765b309bccdaf47a4ed3ee0cd3c00f831e11605616da0e177e4090b1604_s390x as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-roxctl-rhel8@sha256:7744d2530bc26d872030805b583141f2aae75d9b119efa344e025c78a4e8b3c1_ppc64le as a component of RHACS 4.3 for RHEL 8
  • advanced-cluster-security/rhacs-roxctl-rhel8@sha256:788627d59ebeaa64b341f704f8f493a0420c0c681b15ffcd419adf993033dd6c_amd64 as a component of RHACS 4.3 for RHEL 8
Summary
A flaw was found in Dex, an identity service that uses OpenID Connect to drive authentication for other apps. This issue may allow an attacker to make a victim navigate to a malicious website and guide 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.
Remediation
If you are using an earlier version of RHACS 4.3, you are advised to upgrade to patch release 4.3.1.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-7166

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

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.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Exposure of Sensitive Information to an Unauthorized Actor → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-200Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-3113Red Hat Advanced Cluster Security: Schwachstelle ermöglicht Offenlegung von Informationen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Advanced Cluster Security ausnutzen, um Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20221012Security Bulletin 12 Oct 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Oct 2022, published on 12 October 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-018362Linux Foundation の dex における認証の欠如に関する脆弱性

Linux Foundation の dex には、認証の欠如に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
dex: < 2.35.0
Fixed
Action
If you are using an earlier version of RHACS 4.3, you are advised to upgrade to patch release 4.3.1.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 Oct 2022 · Last source change 22 Apr 2025, 17:20 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-7166
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 2.35.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 2.35.0 · Fixed: If you are using an earlier version of RHACS 4.3, you are advised to upgrade to patch release 4.3.1.
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2022-7166↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Patch or update reference↗Public exploit reference · GitHub GHSA-VH7G-P26C-J2CW↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-39222 · cve.blacktree.nl