Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Amazon | aws-load-balancer-controller | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Amazon | Aws-load-balancer-controller |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.647% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incorrect behavior order in the Gateway API listener-rule generation in Amazon AWS Load Balancer Controller before 3.4.2 might allow an authenticated remote user to intercept, spoof, or deny another namespace's gRPC traffic on a shared Gateway via a crafted HTTPRoute resource. To mitigate this issue, users should upgrade to version 3.4.2. | |
| Title | Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller | |
| First Time appeared |
Amazon
Amazon aws-load-balancer-controller |
|
| Weaknesses | CWE-653 | |
| CPEs | cpe:2.3:a:amazon:aws-load-balancer-controller:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Amazon
Amazon aws-load-balancer-controller |
|
| References |
| |
| Metrics |
cvssV3_1
|