CVE-2024-10125 Lack of JWT issuer and signer validation
Attackers can bypass authentication by forging JWTs if ALB targets are publicly accessible, as the middleware fails to validate issuer and signer identity.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-10125?
CVE-2024-10125 is a medium-severity authentication bypass vulnerability in Amazon.ApplicationLoadBalancer.Identity.AspNetCore Middleware, published on 21 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Amazon.ApplicationLoadBalancer.Identity.AspNetCore repo https://github.com/awslabs/aws-alb-identity-aspnetcore#validatetokensignature contains Middleware that can be used in conjunction with the Application Load Balancer (ALB) OpenId Connect integration and can be used in any ASP.NET https://dotnet.microsoft.com/apps/aspnet Core deployment scenario, including Fargate, EKS, ECS, EC2, and Lambda. In the JWT handling code, it performs signature validation but fails to validate the JWT issuer and signer identity. The signer omission, if combined with a scenario where the infrastructure owner allows internet traffic to the ALB targets (not a recommended configuration), can allow for JWT signing by an untrusted entity and an actor may be able to mimic valid OIDC-federated sessions to the ALB targets.
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.
Weakness: CWE-290
Which versions are affected by CVE-2024-10125?
How do I fix CVE-2024-10125?
No fix has been published for CVE-2024-10125 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-10125 being exploited?
There is no known exploitation of CVE-2024-10125 in the wild and no public exploit code.