CVE-2024-8901: Lack of JWT issuer and signer validation
The AWS ALB Route Directive Adapter For Istio repo https://github.com/awslabs/aws-alb-route-directive-adapter-for-istio/tree/master provides an OIDC authentication mechanism that was integrated into the open source Kubeflow project. The adapter uses JWT for authentication, but lacks proper signer and issuer validation. In deployments of ALB that ignore security best practices, where ALB targets are directly exposed to internet traffic, an actor can provide a JWT signed by an untrusted entity in order to spoof OIDC-federated sessions and successfully bypass authentication.
The repository/package has been deprecated, is end of life, and is no longer supported. As a security best practice, ensure that your ELB targets (e.g. EC2 Instances, Fargate Tasks etc.) do not have public IP addresses. Ensure any forked or derivative code validate that the signer attribute in the JWT match the ARN of the Application Load Balancer that the service is configured to use.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-8901?
The severity of CVE-2024-8901 is classified as high due to the potential impact on OIDC authentication mechanisms.
How do I fix CVE-2024-8901?
To fix CVE-2024-8901, implement updated authentication and authorization measures for the AWS ALB Route Directive Adapter for Istio.
What systems are affected by CVE-2024-8901?
CVE-2024-8901 affects the AWS ALB Route Directive Adapter for Istio and the Kubeflow project.
What types of vulnerabilities does CVE-2024-8901 address?
CVE-2024-8901 addresses vulnerabilities related to insufficient JWT authentication in OIDC implementations.
Is there a patch for CVE-2024-8901?
Yes, there is a patch available that can be applied to mitigate the vulnerabilities associated with CVE-2024-8901.