Skip to content

mTLS API ordering may skip client authentication

Moderate
lrstewart published GHSA-857q-xmph-p2v5 Aug 9, 2024

Package

s2n-tls

Affected versions

<=v1.4.18

Patched versions

v1.5.0
cargo s2n-tls (Rust)
<0.3.0
0.3.0

Description

Impact

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 s2n_connection_set_config() before calling s2n_connection_set_client_auth_type().

Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted.

Impacted versions: < v1.5.0.

Patches

The patch is included in v1.5.0 [1].

Workarounds

Applications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_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 [email protected]. 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

Severity

Moderate

CVE ID

No known CVE

Weaknesses

No CWEs