Skip to content

Commit

Permalink
This is not a true defense
Browse files Browse the repository at this point in the history
  • Loading branch information
martinthomson committed Sep 1, 2020
1 parent a587bf0 commit 7adbc31
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -6389,13 +6389,13 @@ attack is successful if an attacker can cause a peer to send a UDP datagram to
a host that will perform some action based on content in the datagram.

This section discusses ways in which QUIC might be used for request forgery
attacks and describes countermeasures that can be implemented by QUIC
endpoints. These actions are described on the assumption that potential targets
for request forgery attacks take no action to protect against these attacks.
While target services are encouraged to implement better protections, such as
strong authentication that does not rely on implicit signals, this section
describes mitigations that can be employed unilaterally by a QUIC
implementation or deployment.
attacks.

This section also describes limited countermeasures that can be implemented by
QUIC endpoints. These mitigations can be employed unilaterally by a QUIC
implementation or deployment, without potential targets for request forgery
attacks taking action. However these countermeasures could be insufficient if
UDP-based services do not properly authorize requests.


### Control Options for Endpoints
Expand Down

0 comments on commit 7adbc31

Please sign in to comment.