Security readout for executives and security teams
Plain-English summary
Argo CD could fail to verify TLS certificates when talking to an external OIDC identity provider. In affected versions, a malicious or untrusted provider could be trusted during authentication-related flows, putting Kubernetes delivery control at risk.
Executive priority
Prioritize remediation where Argo CD controls production Kubernetes delivery and uses external OIDC. The issue can undermine trust in authentication infrastructure, but the available source bundle does not prove active exploitation.
Technical view
CVE-2022-31105 is improper certificate validation in Argo CD OIDC provider connections. Affected ranges are >=0.4.0 <2.2.11, >=2.3.0 <2.3.6, and >=2.4.0 <2.4.5. Fixed releases are 2.2.11, 2.3.6, and 2.4.5. CWEs include CWE-295 and CWE-599.
Likely exposure
Highest exposure is Argo CD deployments using an external OIDC provider rather than only the bundled Dex instance. The source bundle does not identify affected managed services or downstream distributions.
Exploitation context
The CVSS score is 8.3 with network attack vector, high complexity, no privileges required, user interaction required, changed scope, and high impact. The bundle does not show CISA KEV listing or cited evidence of active exploitation.
Researcher notes
Focus validation on certificate verification behavior in OIDC paths and whether the deployment uses external OIDC. The named workaround only affects API-server login flows and does not force certificate verification for token validation on API calls.
Mitigation direction
- Upgrade Argo CD to 2.2.11, 2.3.6, 2.4.5, or a later fixed release.
- For external OIDC, set oidc.config.rootCA in argocd-cm as a partial temporary mitigation.
- Do not treat rootCA as complete; token verification on API calls remains unaffected.
- Review the Argo CD advisory and release notes before applying production changes.
Validation and detection
- Inventory Argo CD versions and flag affected 0.4.0, 2.2.x, 2.3.x, and 2.4.x deployments.
- Review argocd-cm for external OIDC configuration and oidc.config.rootCA presence.
- Confirm deployed images are 2.2.11, 2.3.6, 2.4.5, or later fixed releases.
- Check authentication logs for unusual identity-provider or certificate-related events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-599: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31105 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H1.66Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-7943-82jg-wmw5CVE reference · x_refsource_CONFIRM
- https://github.com/argoproj/argo-cd/releases/tag/v2.3.6CVE reference · x_refsource_MISC
- https://github.com/argoproj/argo-cd/releases/tag/v2.4.5CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Validation of OpenSSL Certificate
Missing Validation of OpenSSL Certificate represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.