Revision 8744ba5e4260ccb47daae3c45bb8e7b5bac42cd3 authored by Matt Caswell on 29 May 2015, 16:05:01 UTC, committed by Matt Caswell on 31 May 2015, 23:30:56 UTC
dtls1_get_message has an |mt| variable which is the type of the message that is being requested. If it is negative then any message type is allowed. However the value of |mt| is not checked in one of the main code paths, so a peer can send a message of a completely different type and it will be processed as if it was the message type that we were expecting. This has very little practical consequences because the current behaviour will still fail when the format of the message isn't as expected. Reviewed-by: Andy Polyakov <appro@openssl.org> (cherry picked from commit 8c2b1d872b25f3ec78e04f5cd2de8f21e853c4a6)
1 parent 4d9dc0c
| File | Mode | Size |
|---|---|---|
| HOWTO | ||
| apps | ||
| crypto | ||
| ssl | ||
| README | -rw-r--r-- | 598 bytes |
| c-indentation.el | -rw-r--r-- | 1.6 KB |
| fingerprints.txt | -rw-r--r-- | 2.8 KB |
| openssl-shared.txt | -rw-r--r-- | 1.5 KB |
| openssl.txt | -rw-r--r-- | 45.6 KB |
| openssl_button.gif | -rw-r--r-- | 2.0 KB |
| openssl_button.html | -rw-r--r-- | 239 bytes |
| ssleay.txt | -rw-r--r-- | 276.5 KB |
| standards.txt | -rw-r--r-- | 11.8 KB |
Computing file changes ...
