Improper Certificate Validation Affecting servicemesh-proxy package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.07% (31st 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 IDSNYK-RHEL8-SERVICEMESHPROXY-4400559
  • published26 Mar 2023
  • disclosed23 Feb 2022

Introduced: 23 Feb 2022

CVE-2022-21656  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 servicemesh-proxy.

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 edge and service proxy, designed for cloud-native applications. The default_validator.cc implementation used to implement the default certificate validation routines has a "type confusion" bug when processing subjectAltNames. This processing allows, for example, an rfc822Name or uniformResourceIndicator to be authenticated as a domain name. This confusion allows for the bypassing of nameConstraints, as processed by the underlying OpenSSL/BoringSSL implementation, exposing the possibility of impersonation of arbitrary servers. As a result Envoy will trust upstream certificates that should not be trusted.

CVSS Scores

version 3.1