Advisory

GHSA-857q-xmph-p2v5

Also known as: None

Summary

s2n-tls's mTLS API ordering may skip client authentication

Details

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]](mailto:[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

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-08-09 20:41 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

s2n-tls

crates.io · All systems

Affected

  • introduced 0, fixed 0.3.0 (semver)

Fixed versions

0.3.0

Fix

  • Fixed version 0.3.0
    cargo update -p s2n-tls --precise 0.3.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences