Potential denial of service after connection migration
LowPublished Jul 24, 2023
### Impact An issue in s2n-quic results in the endpoint shutting down due to a combination of peer-initiated connection migration and duplicate new connection ID frames being received. No AWS services are affected by this issue, and customers of AWS services do not need to take action. Impacted versions: <=v1.24.0 ### Patches The patch is included in v1.25.0. ### Workarounds There is no workaround. Applications using s2n-quic should upgrade their application to the most recent release of s2n-quic. If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| s2n-quic crates.io | < v1.25.0 | v1.25.0 |
Details and references
- Severity from
- GitHub (reviewed advisory)
More AWS advisories
All AWS| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Dec 212023 | Potential URI resolution path traversal in the AWS SDK for PHP Medium6.0Dec 21, 2023 | Medium6.0 | 3.288.1 |
| Nov 62023 | Potential denial of service via crafted stream framesLowNov 6, 2023 | Low | v1.31.0 |
| Oct 52023 | s2n-tls could negotiate signature algorithms not allowed by policyLowOct 5, 2023 | Low | 1.3.54 |
| Jun 302023 | Potential denial of service when receiving empty UDP packetsMediumJun 30, 2023 | Medium | v1.23.0 |
| Jun 192023 | EKS overly permissive trust policiesMedium6.6Jun 19, 2023 | Medium6.6 | 2.80.0+1 more |
| Feb 142023 | Issue with parsing Certificate Common Name (CN) in s2n-tlsLowFeb 14, 2023 | Low | v1.3.35 |