Skip to content
AWSGHSA-97r4-p6c4-5gv3

s2n-tls could negotiate signature algorithms not allowed by policy

LowPublished Oct 5, 2023

### Impact s2n-tls clients and servers negotiating TLS1.2 could choose a SHA-1 hash in TLS connection signatures despite their s2n-tls security policy not supporting SHA-1. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. ### Patches The patch is included in s2n-tls v1.3.54 ### Workarounds There is no workaround. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.

GitHub advisory

Affected versions

PackageAffectedFixed in
s2n-tls
Product
< 1.3.541.3.54
Details and references

More AWS advisories

All AWS
Advisory
GHSA for sagemaker.base_deserializers.NumpyDeserializer
High7.8May 2, 2024
Potential URI resolution path traversal in the AWS SDK for PHP
Medium6.0Dec 21, 2023
Potential denial of service via crafted stream frames
LowNov 6, 2023
Potential denial of service after connection migration
LowJul 24, 2023
Potential denial of service when receiving empty UDP packets
MediumJun 30, 2023
EKS overly permissive trust policies
Medium6.6Jun 19, 2023

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.