Issue with parsing Certificate Common Name (CN) in s2n-tls
LowPublished Feb 14, 2023
An issue in s2n-tls results in skipping a certificate’s Common Name field validation if it exceeds 255 bytes. As a result, s2n-tls incorrectly validates a certificate that has a Common Name (CN) larger than 255 bytes, doesn’t have a Subject Alternative Name (SAN), and is signed by a trusted Certificate Authority (CA). No AWS services are affected by this issue and customers of AWS services do not need to take action. Client applications using s2n-tls should upgrade their application to the most recent release of s2n-tls. Impacted versions: All versions of s2n-tls from commit e954e6e through commit 4bd1505. Affected s2n-tls users should fetch s2n-tls commit a58b308 or later.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| s2n-tls Product | < v1.3.35 | v1.3.35 |
Details and references
- Severity from
- GitHub (reviewed advisory)
More AWS advisories
All AWS| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jul 242023 | Potential denial of service after connection migration | Low | v1.25.0 |
| Jun 302023 | Potential denial of service when receiving empty UDP packets | Medium | v1.23.0 |
| Jun 192023 | EKS overly permissive trust policies | Medium6.6 | 2.80.0+1 more |
| Dec 102022 | Privilege Escalation Vector in CloudWatch Agent for Windows | High7.1 | 1.247355 |
| Sep 272022 | Issue with configuring session ticket names in s2n-tls | Medium | v1.3.23 |
| Sep 272022 | Server denial-of-service by using sslv2 message format in a HelloRetryRequest handshake | Low | <v1.3.23 |