Incorrect Authorization Affecting servicemesh-proxy package, versions <0:1.1.17-2.el8


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.11% (44th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Incorrect Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-SERVICEMESHPROXY-4399305
  • published26 Mar 2023
  • disclosed24 Aug 2021

Introduced: 24 Aug 2021

CVE-2021-32779  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade RHEL:8 servicemesh-proxy to version 0:1.1.17-2.el8 or higher.
This issue was patched in RHSA-2021:3273.

NVD Description

Note: Versions mentioned in the description apply only to the upstream servicemesh-proxy package and not the servicemesh-proxy package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy incorrectly handled a URI '#fragment' element as part of the path element. Envoy is configured with an RBAC filter for authorization or similar mechanism with an explicit case of a final "/admin" path element, or is using a negative assertion with final path element of "/admin". The client sends request to "/app1/admin#foo". In Envoy prior to 1.18.0, or 1.18.0+ configured with path_normalization=false. Envoy treats fragment as a suffix of the query string when present, or as a suffix of the path when query string is absent, so it evaluates the final path element as "/admin#foo" and mismatches with the configured "/admin" path element. In Envoy 1.18.0+ configured with path_normalization=true. Envoy transforms this to /app1/admin%23foo and mismatches with the configured /admin prefix. The resulting URI is sent to the next server-agent with the offending "#foo" fragment which violates RFC3986 or with the nonsensical "%23foo" text appended. A specifically constructed request with URI containing '#fragment' element delivered by an untrusted client in the presence of path based request authorization resulting in escalation of Privileges when path based request authorization extensions. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes that removes fragment from URI path in incoming requests.

CVSS Scores

version 3.1