<p>Upgrade <code>Oracle:8</code> <code>olcne-kubevirt-chart</code> to version 0:1.6.1-9.el8 or higher.<br>This issue was patched in <code>ELSA-2023-23648</code>.</p>

CVE-2023-27488 Affecting olcne-kubevirt-chart package, versions <0:1.6.1-9.el8

Threat Intelligence

0.23% (62^nd 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 ID SNYK-ORACLE8-OLCNEKUBEVIRTCHART-6593746
published 10 Apr 2024
disclosed 4 Apr 2023

Report a new vulnerability Found a mistake?

Introduced: 4 Apr 2023

CVE-2023-27488 Open this link in a new tab

How to fix?

Upgrade Oracle:8 olcne-kubevirt-chart to version 0:1.6.1-9.el8 or higher.
This issue was patched in ELSA-2023-23648.

NVD Description

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

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, escalation of privileges is possible when failure_mode_allow: true is configured for ext_authz filter. For affected components that are used for logging and/or visibility, requests may not be logged by the receiving service.

When Envoy was configured to use ext_authz, ext_proc, tap, ratelimit filters, and grpc access log service and an http header with non-UTF-8 data was received, Envoy would generate an invalid protobuf message and send it to the configured service. The receiving service would typically generate an error when decoding the protobuf message. For ext_authz that was configured with failure_mode_allow: true, the request would have been allowed in this case. For the other services, this could have resulted in other unforeseen errors such as a lack of visibility into requests.

As of versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, Envoy by default sanitizes the values sent in gRPC service calls to be valid UTF-8, replacing data that is not valid UTF-8 with a ! character. This behavioral change can be temporarily reverted by setting runtime guard envoy.reloadable_features.service_sanitize_non_utf8_strings to false. As a workaround, one may set failure_mode_allow: false for ext_authz.

References

CVSS Scores

version 3.1

Attack Vector (AV)

Network
Attack Complexity (AC)

Low
Privileges Required (PR)

None
User Interaction (UI)

None

Scope (S)

Unchanged

Confidentiality (C)

High
Integrity (I)

High
Availability (A)

High