1764788 - TLS 1.3 Wrong undefined content type record layer alerts

Status: RESOLVED FIXED

(NSS :: Libraries, enhancement)

Description

[Leander Schwarz]

• [S] upon receiving a record with an undefined content type at the beginning of the handshake. NSS sends an 'illegal parameter' alert upon receiving a record with an undefined content type during the handshake, NSS sends a 'decode error'.

• [C] upon receiving a record with invalid content type (0xFF), NSS responds with a 'decode error' alert.

The relevant RFC section:

RFC 8446 - 5. Record Protocol
If a TLS implementation receives an unexpected record type, it MUST terminate the
connection with an "unexpected_message" alert.

The bugs were originally reported in Bug 1714579.

Comment 1

[Leander Schwarz]

Attachment: Bug 1764788 - Correct invalid record inner and outter content type alerts. r?djackson

Added test cases for alerts during and pre handshake as well as TLS 1.3 only after handshake (application data) cases due to unsupported de- and encryption of lower TLS version records in gtest.

Adjusted some test cases that expect failed connections to the updated alerts.

Depends on D141841

Comment 2

[Dennis Jackson]

https://hg.mozilla.org/projects/nss/rev/7f4b0af3a526e801a977831ef23f82e4e66d6b8a