Re: AD review of draft-ietf-imapapnd-appendlimit-extension-06
Alexey Melnikov <[email protected]> Fri, 18 Dec 2015 11:40:08 +0000
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
On 17/12/2015 23:20, Barry Leiba wrote: >> Say a server has a limit of 50 MB. Before this extension, an attacker >> first tries to APPEND 25 MB and it succeeds. >> Then he tries 40MB and that too succeeds. Finally he tries 60 MB to >> find the limit of server and use that as start of attack. With this extension >> the attacker can find the limit in no time, making it easy for him to >> attack. > OK, I see the point now. It seems a little thin (but, then, the > document does already say it is) -- I can just try to append 300MB, > using non-synch literal, right from the start. > > But perhaps this will be more satisfying: > > OLD > The IMAP APPENDLIMIT extension described in this document can > conceivably be used to facilitate Denial-of-Service attacks. > Specifically, the information contained in the APPENDLIMIT capability > and use of the APPEND command make it somewhat quicker and easier to > devise an efficacious Denial-of-Service attack. However, unless > implementations are very weak, these extensions do not create any > vulnerability that has not always existed with IMAP. > NEW > The IMAP APPENDLIMIT extension described in this document can > conceivably be used to facilitate Denial-of-Service attacks by allowing > an attacker to home in on a critical value right away. The attacker > might want to send a large data block to the server repeatedly, > forcing the server to process the block, but would not want to limit > the scope of its attack by filling an actual mailbox with successful > appends. Without this extension, the attacker needs to guess: a > too-small guess results in an appended message that takes up the > user's quota, while a far-too-large guess might simply cause the > server to terminate the connection because of suspected abuse. > > But with this extension, the attacker can immediately choose a > value that's a little too large, but not so much as to trigger an "abuse" > response, making it easier to mount such an attack. > > To mitigate this extension's input to such an attack, a server might > take a harder line on message sizes that are above the APPENDLIMIT > value -- because the client knows the limit and should not even be > trying to send such commands, a server might consider even a single > attempt to be abusive, and terminate the IMAP connection straight > away. > END > > How's that work for you? I think this is fine. There is still a problem with clients that don't observe APPENDLIMIT and are used by a significant portion by MSP users, but hopefully pressure on vendors can help with that. _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext