{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-10125 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10125 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-10125 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2024-10125 in the wild and no public exploit code.\n\nAffected product: Amazon.ApplicationLoadBalancer.Identity.AspNetCore Middleware. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-10125/ (Markdown: https://insights.sbomify.com/CVE-2024-10125/index.md)","id":"CVE-2024-10125","markdown":"https://insights.sbomify.com/CVE-2024-10125/index.md","name":"CVE-2024-10125","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"AWS ALB Identity Middleware","requires_auth":"none","summary":"Attackers can bypass authentication by forging JWTs if ALB targets are publicly accessible, as the middleware fails to validate issuer and signer identity.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"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.\n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Lack of JWT issuer and signer validation","id":"CVE-2024-10125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Local file inclusion vulnerability in M-Files Server","id":"CVE-2024-10126"},"packages":[],"prev":{"headline":"Missing authorization in Vayu Blocks – Website Builder for the Block Editor","id":"CVE-2024-10124"},"products":["Amazon.ApplicationLoadBalancer.Identity.AspNetCore Middleware"],"published":"2024-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["Amazon"]},"summary":"Attackers can bypass authentication by forging JWTs if ALB targets are publicly accessible, as the middleware fails to validate issuer and signer identity.","url":"https://insights.sbomify.com/CVE-2024-10125/"}