ex_aws_sns SigningCertURL not validated in verify_message/1
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.3.5 and 1853d280b152d10384a1e21a22cf22152a60be48.
Improper Certificate Validation vulnerability in ex-aws ex_aws_sns (ExAws.SNS, ExAws.SNS.PublicKeyCache modules) allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/ex_aws/sns.ex, lib/ex_aws/sns/public_key_cache.ex and program routines ExAws.SNS.verify_message/1, ExAws.SNS.PublicKeyCache.get/1. ExAws.SNS.verify_message/1 fetches the signing certificate from the SigningCertURL field of the incoming SNS message without validating that the URL uses HTTPS or that the host matches an AWS-owned SNS certificate domain. An unauthenticated attacker who can POST to an endpoint that calls verify_message/1 can supply an attacker-controlled SigningCertURL, sign a forged SNS message with their own key, and cause the function to return :ok, completely bypassing SNS signature verification. This issue affects ex_aws_sns: from 2.0.0 before 2.3.5.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ex-aws | >=2.0.0 <2.3.5, >=a7ec21880943f4dac1d59bda557db0ffcd2b61fa <1853d280b152d10384a1e21a22cf22152a60be48 | 2.3.5, 1853d280b152d10384a1e21a22cf22152a60be48 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket