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`.

The version of ecs-service-connect-agent installed on the remote host is prior to v1.25.4.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2023-003 advisory.

  - 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. (CVE-2023-27487)

  - 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`. (CVE-2023-27488)

  - Envoy is an open source edge and service proxy designed for cloud-native applications. Compliant HTTP/1     service should reject malformed request lines. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and     1.22.9, There is a possibility that non compliant HTTP/1 service may allow malformed requests, potentially     leading to a bypass of security policies. This issue is fixed in versions 1.26.0, 1.25.3, 1.24.4, 1.23.6,     and 1.22.9. (CVE-2023-27491)

  - 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 Lua filter is vulnerable to denial of service. Attackers     can send large request bodies for routes that have Lua filter enabled and trigger crashes. As of versions     versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, Envoy no longer invokes the Lua coroutine if the     filter has been reset. As a workaround for those whose Lua filter is buffering all requests/ responses,     mitigate by using the buffer filter to avoid triggering the local reply in the Lua filter.
    (CVE-2023-27492)

  - 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, Envoy does not sanitize or escape request properties when     generating request headers. This can lead to characters that are illegal in header values to be sent to     the upstream service. In the worst case, it can cause upstream service to interpret the original request     as two pipelined requests, possibly bypassing the intent of Envoy's security policy. Versions 1.26.0,     1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. As a workaround, disable adding request headers based     on the downstream request properties, such as downstream certificate properties. (CVE-2023-27493)

  - 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 OAuth filter assumes that a `state` query param is present     on any response that looks like an OAuth redirect response. Sending it a request with the URI path     equivalent to the redirect path, without the `state` parameter, will lead to abnormal termination of Envoy     process. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. The issue can also be     mitigated by locking down OAuth traffic, disabling the filter, or by filtering traffic before it reaches     the OAuth filter (e.g. via a lua script). (CVE-2023-27496)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2023-23649 advisory.

    - CVE-2023-27496
    - CVE-2023-27488
    - CVE-2023-27493
    - CVE-2023-27492
    - CVE-2023-27491
    - CVE-2023-27487

    * [1.6.1-3]

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-165 advisory.

  - 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. (CVE-2023-27487)

  - 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`. (CVE-2023-27488)

  - Envoy is an open source edge and service proxy designed for cloud-native applications. Compliant HTTP/1     service should reject malformed request lines. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and     1.22.9, There is a possibility that non compliant HTTP/1 service may allow malformed requests, potentially     leading to a bypass of security policies. This issue is fixed in versions 1.26.0, 1.25.3, 1.24.4, 1.23.6,     and 1.22.9. (CVE-2023-27491)

  - 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 Lua filter is vulnerable to denial of service. Attackers     can send large request bodies for routes that have Lua filter enabled and trigger crashes. As of versions     versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, Envoy no longer invokes the Lua coroutine if the     filter has been reset. As a workaround for those whose Lua filter is buffering all requests/ responses,     mitigate by using the buffer filter to avoid triggering the local reply in the Lua filter.
    (CVE-2023-27492)

  - 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, Envoy does not sanitize or escape request properties when     generating request headers. This can lead to characters that are illegal in header values to be sent to     the upstream service. In the worst case, it can cause upstream service to interpret the original request     as two pipelined requests, possibly bypassing the intent of Envoy's security policy. Versions 1.26.0,     1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. As a workaround, disable adding request headers based     on the downstream request properties, such as downstream certificate properties. (CVE-2023-27493)

  - 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 OAuth filter assumes that a `state` query param is present     on any response that looks like an OAuth redirect response. Sending it a request with the URI path     equivalent to the redirect path, without the `state` parameter, will lead to abnormal termination of Envoy     process. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. The issue can also be     mitigated by locking down OAuth traffic, disabling the filter, or by filtering traffic before it reaches     the OAuth filter (e.g. via a lua script). (CVE-2023-27496)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
178286	Amazon Linux 2 : ecs-service-connect-agent (ALASECS-2023-003)	Nessus	Amazon Linux Local Security Checks	critical
176422	Oracle Linux 7 : olcne (ELSA-2023-23649)	Nessus	Oracle Linux Local Security Checks	critical
175073	Amazon Linux 2023 : ecs-service-connect-agent (ALAS2023-2023-165)	Nessus	Amazon Linux Local Security Checks	critical

Detections

Analytics

CVE-2023-27488

critical

Tenable Plugins

critical

critical

critical