Thaidn

Traefik is a HTTP reverse proxy and load balancer. In versions >= v3.7.0 and <= v3.7.11, the Kubernetes ingress-nginx provider mishandles Ingresses that carry both an authentication annotation and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation. For such Ingresses the provider creates an additional 'sibling' router that matches on the host alone, carries only the RedirectRegex middleware, and still points at the parent router's protected backend service. Because RedirectRegex is not a terminal handler, a request its pattern does not match is forwarded to the backend, and because the redirect pattern only accepts a numeric port while Traefik's host matcher canonicalizes the authority via net.SplitHostPort, a request with a non-numeric or empty port (for example 'Host: www.example.com:x') selects the sibling router, misses the redirect, and is proxied to the protected backend with none of the Ingress's annotation-derived middlewares applied. This discards not only authentication (e.g. BasicAuth) but every annotation-derived middleware, including source-IP allowlisting. Traefik v2 and v3 releases before v3.7.0 are not affected. The issue is fixed in v3.7.12.

**Name of the Vulnerable Software and Affected Versions** AWS Encryption SDKs versions prior to 2.0.0 **Description** A weak robustness vulnerability exists in the AWS Encryption SDKs due to the non-committing property of AES-GCM and other AEAD ciphers. This allows an attacker to craft a unique ciphertext that decrypts to multiple different results, particularly in a multi-recipient setting. The vulnerability also enables information leakage and ciphertext forgery attacks. An attacker can create ciphertexts that leak the user's AWS account ID, encryption context, user agent, and IP address upon decryption. Additionally, an attacker can create ciphertexts that are accepted by other users. The non-committing property of AES-GCM can cause nonidentical plaintexts when decrypting a single ciphertext with two different keys. **Recommendations** Update the AWS Encryption SDK to version 2.0.0 or later to fix the vulnerability. This new version includes a breaking change that addresses the issue. All users are recommended to upgrade to this version to mitigate the risk of exploitation.