Security readout for executives and security teams
Plain-English summary
Envoy's OAuth filter could let a request through when it carried any access token, because Envoy did not validate that token before assuming authentication succeeded. A protected service using affected Envoy versions could expose data or actions without a real login. The vendor advises upgrading; sources state no workaround.
Executive priority
Treat as urgent for any environment where Envoy enforces user access to sensitive applications. The business risk is unauthorized access, not service disruption. Patch prioritization should focus first on externally reachable and high-value protected services.
Technical view
In Envoy before 1.22.1, the OAuth filter lacked access-token validation. When the HMAC-signed cookie was absent, Envoy should have started the full authentication flow, but instead treated the presence of an access token as sufficient. CVSS 10.0 reflects unauthenticated network access, low complexity, changed scope, and high confidentiality and integrity impact.
Likely exposure
Exposure is limited to Envoy deployments before 1.22.1 that use the OAuth filter to protect upstream applications or routes. Organizations running Envoy only for unrelated proxying features are not shown as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The issue is still high urgency because exploitation would be remote, unauthenticated, low complexity, and could bypass the intended login flow for protected services.
Researcher notes
This is a CWE-306 missing-authentication issue in Envoy's OAuth filter logic. The provided evidence supports affected versions before 1.22.1, upgrade guidance, and no known workaround. It does not prove exploitation in the wild or identify downstream distributions beyond envoyproxy/envoy.
Mitigation direction
- Upgrade Envoy to 1.22.1 or later.
- Prioritize internet-facing Envoy OAuth filter deployments.
- Check vendor advisory before relying on compensating controls.
- Do not use the affected OAuth filter as the sole gate while awaiting upgrade.
Validation and detection
- Inventory Envoy versions across gateways, sidecars, and edge proxies.
- Identify configurations using Envoy's OAuth filter.
- Confirm protected routes no longer run Envoy versions before 1.22.1.
- Review access logs for token-bearing requests without expected signed cookies.
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-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-29226 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
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
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:L/PR:N/UI:N/S:C/C:H/I:H/A:N3.95.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/envoyproxy/envoy/commit/7ffda4e809dec74449ebc330cebb9d2f4ab61360CVE reference · x_refsource_MISC
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-h45c-2f94-prxhCVE reference · x_refsource_CONFIRM
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.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.