Skip to content
Fencer Vulns
critical 10.0

CVE-2022-29226 json

Trivial authentication bypass in Envoy

published 2022-06-09 4 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2022-29226 , EUVD-2022-33588 , GHSA-h45c-2f94-prxh

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

Envoy is a cloud-native high-performance proxy. In versions prior to 1.22.1 the OAuth filter implementation does not include a mechanism for validating access tokens, so by design when the HMAC signed cookie is missing a full authentication flow should be triggered. However, the current implementation assumes that access tokens are always validated thus allowing access in the presence of any access token attached to the request. Users are advised to upgrade. There is no known workaround for this issue.

Patch / fix

  • bitnami envoy 1.22.1
  • envoyproxy envoy 1.22.1
  • servicemesh service mesh 2.1 2.1.3-1.el8
  • servicemesh-cni service mesh 2.1 2.1.3-1.el8
  • servicemesh-proxy service mesh 2.1 2.1.3-1.el8
  • servicemesh-operator service mesh 2.1 2.1.3-2.el8
  • servicemesh-ratelimit service mesh 2.1 2.1.3-1.el8
  • servicemesh-prometheus service mesh 2.1 2.23.0-7.el8
  • servicemesh-proxy-wasm service mesh 2.1 2.1.3-1.el8
  • servicemesh-pilot-agent service mesh 2.1 2.1.3-1.el8

red hat advisories RHSA-2022:5004

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-29226 updated cvss 10.0

envoy: oauth filter allows trivial bypass

  • Red Hat OpenShift Service Mesh 2.1 servicemesh-proxy 2.1.3-1.el8, servicemesh-proxy-wasm 2.1.3-1.el8
    fixed: vendor fix “There is no known mitigation for this flaw.” RHSA-2022:5004
  • Red Hat OpenShift Service Mesh 2.0 servicemesh-proxy Red Hat OpenShift Service Mesh 2.1 servicemesh 2.1.3-1.el8, servicemesh-cni 2.1.3-1.el8, servicemesh-operator 2.1.3-2.el8, servicemesh-ratelimit 2.1.3-1.el8, servicemesh-pilot-agent 2.1.3-1.el8, servicemesh-prometheus 2.23.0-7.el8, +1 more
    not affected: vulnerable code not present “There is no known mitigation for this flaw.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
18 mo ago

Exploit prediction

1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
OSV 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
bitnami envoy
<1.22.1
1.22.1

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.