Skip to content

crypto/tls: QUIC Transport Parameters Mutation via HRR #78751

Description

@thatnealpatel

A client sends QUIC transport parameters in its ClientHello, when a hello retry happens it sends a new ClientHello, and we don't validate that the second ClientHello has the same parameters as the first. We don't do anything with the parameters from the first ClientHello, they just get replaced with the new ones prior to passing them to the QUIC stack.

This is not a security issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugReportIssues describing a possible bug in the Go implementation.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions