An API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2nconnectionsetconfig() before calling s2nconnectionsetclientauthtype().
Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2nconfigsetclientauth_type(). s2n-tls clients verifying server certificates are not impacted.
Impacted versions: < v1.5.0.
The patch is included in v1.5.0 [1].
Applications can workaround this issue by calling s2nconnectionsetconfig() after calling s2nconnectionsetclientauthtype(), or by enabling client authentication on the config with s2nconfigsetclientauth_type().
If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
[1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0
[2] https://aws.amazon.com/security/vulnerability-reporting
{ "nvd_published_at": null, "cwe_ids": [ "CWE-287" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-08-09T20:41:38Z" }