CVE-2023-27487 Affecting olcne-api-server package, versions <0:1.6.1-9.el8


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.25% (64th 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-ORACLE8-OLCNEAPISERVER-6593603
  • published10 Apr 2024
  • disclosed4 Apr 2023

Introduced: 4 Apr 2023

CVE-2023-27487  (opens in a new tab)

How to fix?

Upgrade Oracle:8 olcne-api-server to version 0:1.6.1-9.el8 or higher.
This issue was patched in ELSA-2023-12354.

NVD Description

Note: Versions mentioned in the description apply only to the upstream olcne-api-server package and not the olcne-api-server 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, the client may bypass JSON Web Token (JWT) checks and forge fake original paths. The header x-envoy-original-path should be an internal header, but Envoy does not remove this header from the request at the beginning of request processing when it is sent from an untrusted client. The faked header would then be used for trace logs and grpc logs, as well as used in the URL used for jwt_authn checks if the jwt_authn filter is used, and any other upstream use of the x-envoy-original-path header. Attackers may forge a trusted x-envoy-original-path header. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 have patches for this issue.

CVSS Scores

version 3.1