Re: [TLS] 0-RTT and Anti-Replay

[Mohamad Badra <[e-mail]>]

Hi Eric,


> Client                        Attacker                          Server
>
> ClientHello [+0-RTT] ------------>
> "POST /buy-something" ----------->
>
>                               ClientHello [+0-RTT] --------------->
>                               "POST /buy-something" -------------->
>
>                                                    [Processes purchase]
>                                  <---------- ServerHello [accept 0-RTT]
>                                                   (+ rest of handshake)
>
>
> The attacker just discards the server's response and then the server
> somehow forces the server to reboot (this is the hard part).
>
> Once the server has rebooted, the attacker re-sends the client's
> initial flight then just forwards data back and forth to the client.
>
> Client                        Attacker                          Server
>                               ClientHello [+0-RTT] --------------->
>                               "POST /buy-something" -------------->
>
>    <--------------------------------------  ServerHello [reject 0-RTT]
>                                                  (+ rest of handshake)
>
> Finished --------------------------------------------------------->
> "Post /buy-something" -------------------------------------------->
>                                                   [Processes purchase]
>
> At this point, you've mounted a successful replay attack. Obviously
> this is not that great an attack because it requires you to be able to
> force a reboot and also get in under the client's timeout window.
>


According to draft-rescorla-tls13-new-flows-01:

   The EncryptedExtensions MUST include an ART indicator that matches
   the client's ART so that the client knows that the 0-RTT handshake
   was successful and that the client's application_data was accepted.



I wonder why the Server doesn't include an indicator in his reject
(encrypted indicator) so the client will avoid sending its request again.

(BTW, based on what a server can reject after a reboot)

Best regards
Mohamad