Missing validation of the outer content_type byte on TLS 1.3 encrypted records in s2n-tls allows an active man-in-the-middle to silently discard individual application data records without either end…
Summary
Missing validation of the outer content_type byte on TLS 1.3 encrypted records in s2n-tls allows an active man-in-the-middle to silently discard individual application data records without either endpoint detecting the modification. RFC 8446 Section 5.2 requires that the outer content_type of all encrypted TLS 1.3 records must be application_data (0x17). The s2n-tls AEAD implementation hardcodes this value in the additional authenticated data rather than using the actual wire byte, so the outer…
In-depth triage · Auto channel
No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).
Lint boundary warnings (1)
The following non-blocking warnings were raised during the lint phase of this triage (e.g. reference URLs not yet on the allowlist). They do not affect entry usability and are disclosed for transparency (see DR-002).
-
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://aws.amazon.com/security/security-bulletins/2026-062-aws/
Sources
- NVD DATABASE
Original Links
- https://aws.amazon.com/security/security-bulletins/2026-062-aws/
- https://github.com/aws/s2n-tls/releases/tag/v1.7.6
- https://github.com/aws/s2n-tls/security/advisories/GHSA-684c-v35q-fvx7
Timeline
- nvd_ingest NVD