Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 applicationsUpgrade envoyproxy/envoy
to version 1.30.8, 1.31.4, 1.32.2 or higher.
Affected versions of this package are vulnerable to Always-Incorrect Control Flow Implementation. An attacker can cause the application to crash by providing non-IP address data in the additional address field. This is only exploitable if Happy Eyeballs is enabled and the IP configuration is not properly validated.
This vulnerability can be mitigated by disabling Happy Eyeballs or changing the IP configuration.
- clusterName: outbound|80||echo.default.svc.cluster.local
endpoints:
- lbEndpoints:
- endpoint:
additionalAddresses:
- address:
envoyInternalAddress:
endpointId: '[fd00:10:244::10]:80'
serverListenerName: connect_originate
address:
envoyInternalAddress:
endpointId: [10.244.0.16:80](http://10.244.0.16/)
serverListenerName: connect_originate
healthCheckConfig: {}
healthStatus: HEALTHY
loadBalancingWeight: 1
metadata:
filterMetadata:
envoy.filters.listener.original_dst:
local: [10.244.0.16:80](http://10.244.0.16/)
envoy.transport_socket_match:
tunnel: http
istio:
workload: echo;default;echo;;Kubernetes
loadBalancingWeight: 1
locality: {}
policy:
overprovisioningFactor: 140