CVSS: 8.3EPSS: 0%CPEs: 4EXPL: 0CVE-2021-29492 – Bypass of path matching rules using escaped slash characters
https://notcve.org/view.php?id=CVE-2021-29492
Envoy is a cloud-native edge/middle/service proxy. Envoy does not decode escaped slash sequences `%2F` and `%5C` in HTTP URL paths in versions 1.18.2 and before. A remote attacker may craft a path with escaped slashes, e.g. `/something%2F..%2Fadmin`, to bypass access control, e.g. a block on `/admin`. A backend server could then decode slash sequences and normalize path and provide an attacker access beyond the scope provided for by the access control policy. ### Impact Escalation of Privileges when using RBAC or JWT filters with enforcement based on URL path. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-4987-27fx-x6cf https://access.redhat.com/security/cve/CVE-2021-29492 https://bugzilla.redhat.com/show_bug.cgi?id=1951188 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CWE-863: Incorrect Authorization •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 1CVE-2021-28682 – envoyproxy/envoy: integer overflow handling large grpc-timeouts
https://notcve.org/view.php?id=CVE-2021-28682
An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable integer overflow in which a very large grpc-timeout value leads to unexpected timeout calculations. Se detectó un problema en Envoy versiones hasta 1.71.1. presenta un desbordamiento de enteros explotable remoto en el que un valor de grpc-timeout muy grande conlleva a cálculos de tiempo de espera inesperados A flaw was found in envoyproxy/envoy. An attacker, able to craft a packet which specifies a large grpc-timeout, can potentially cause envoy to incorrectly calculate the timeouts resulting in a denial of service. • https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/blob/15e3b9dbcc9aaa9d391fa8033904aad1ea1ae70d/api/envoy/api/v2/cluster.proto#L36 https://github.com/envoyproxy/envoy/releases https://github.com/envoyproxy/envoy/security/advisories/GHSA-r22g-5f3x-xjgg https://access.redhat.com/security/cve/CVE-2021-28682 https://bugzilla.redhat.com/show_bug.cgi?id=1942272 • CWE-190: Integer Overflow or Wraparound •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-29258 – envoyproxy/envoy: crash with empty HTTP/2 metadata map
https://notcve.org/view.php?id=CVE-2021-29258
An issue was discovered in Envoy 1.14.0. There is a remotely exploitable crash for HTTP2 Metadata, because an empty METADATA map triggers a Reachable Assertion. Se detectó un problema en Envoy versión 1.14.0. Se presenta un bloqueo explotable remoto para unos metadatos HTTP2, porque un mapa de METADATOS vacío desencadena un Reachable Assertion A flaw was found in envoyproxy. An attacker, able to craft an HTTP2 request that specifies an empty metadata map, can crash envoy resulting in a denial of service due to the null reference. • https://blog.envoyproxy.io https://github.com/envoyproxy/envoy-setec/pull/230 https://github.com/envoyproxy/envoy/releases/tag/v1.14.0 https://github.com/envoyproxy/envoy/security/advisories/GHSA-rqvq-hxw5-776j https://github.com/envoyproxy/envoy/security/advisories/GHSA-xw4q-6pj2-5gfg https://access.redhat.com/security/cve/CVE-2021-29258 https://bugzilla.redhat.com/show_bug.cgi?id=1942280 • CWE-476: NULL Pointer Dereference CWE-617: Reachable Assertion •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-28683 – envoyproxy/envoy: NULL pointer dereference in TLS alert code handling
https://notcve.org/view.php?id=CVE-2021-28683
An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable NULL pointer dereference and crash in TLS when an unknown TLS alert code is received. Se detectó un problema en Envoy versiones hasta 1.71.1. Se presenta una desreferencia de puntero NULL explotable remoto y bloqueo en TLS cuando es recibido un código de alerta TLS desconocido A NULL pointer dereference vulnerability was found envoyproxy/envoy. This flaw allows an attacker to establish a TLS session that sends an invalid TLS alert code, causing a NULL pointer exception to occur that crashes the application, resulting in a denial of service. • https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/releases https://github.com/envoyproxy/envoy/security/advisories/GHSA-r22g-5f3x-xjgg https://github.com/envoyproxy/envoy/security/advisories/GHSA-xw4q-6pj2-5gfg https://access.redhat.com/security/cve/CVE-2021-28683 https://bugzilla.redhat.com/show_bug.cgi?id=1942263 • CWE-476: NULL Pointer Dereference •
CVSS: 8.2EPSS: 0%CPEs: 1EXPL: 0CVE-2021-21378 – JWT authentication bypass with unknown issuer token
https://notcve.org/view.php?id=CVE-2021-21378
Envoy is a cloud-native high-performance edge/middle/service proxy. In Envoy version 1.17.0 an attacker can bypass authentication by presenting a JWT token with an issuer that is not in the provider list when Envoy's JWT Authentication filter is configured with the `allow_missing` requirement under `requires_any` due to a mistake in implementation. Envoy's JWT Authentication filter can be configured with the `allow_missing` requirement that will be satisfied if JWT is missing (JwtMissed error) and fail if JWT is presented or invalid. Due to a mistake in implementation, a JwtUnknownIssuer error was mistakenly converted to JwtMissed when `requires_any` was configured. So if `allow_missing` was configured under `requires_any`, an attacker can bypass authentication by presenting a JWT token with an issuer that is not in the provider list. • https://github.com/envoyproxy/envoy/commit/ea39e3cba652bcc4b11bb0d5c62b017e584d2e5a https://github.com/envoyproxy/envoy/pull/15194 https://github.com/envoyproxy/envoy/security/advisories/GHSA-4996-m8hf-hj27 • CWE-287: Improper Authentication CWE-303: Incorrect Implementation of Authentication Algorithm •