Authorization Bypass Through User-Controlled Key Affecting ecs-service-connect-agent package, versions <0:v1.29.9.0-1.amzn2023


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (19th 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 Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2023-ECSSERVICECONNECTAGENT-8381772
  • published15 Nov 2024
  • disclosed20 Sept 2024

Introduced: 20 Sep 2024

CVE-2024-45806  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 ecs-service-connect-agent to version 0:v1.29.9.0-1.amzn2023 or higher.
This issue was patched in ALAS2023-2024-758.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ecs-service-connect-agent package and not the ecs-service-connect-agent package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

Envoy is a cloud-native high-performance edge/middle/service proxy. A security vulnerability in Envoy allows external clients to manipulate Envoy headers, potentially leading to unauthorized access or other malicious actions within the mesh. This issue arises due to Envoy's default configuration of internal trust boundaries, which considers all RFC1918 private address ranges as internal. The default behavior for handling internal addresses in Envoy has been changed. Previously, RFC1918 IP addresses were automatically considered internal, even if the internal_address_config was empty. The default configuration of Envoy will continue to trust internal addresses while in this release and it will not trust them by default in next release. If you have tooling such as probes on your private network which need to be treated as trusted (e.g. changing arbitrary x-envoy headers) please explicitly include those addresses or CIDR ranges into internal_address_config. Successful exploitation could allow attackers to bypass security controls, access sensitive data, or disrupt services within the mesh, like Istio. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS Scores

version 3.1