DoS exploit in openssl (Debian stable only)
web.nvd.nist.gov
DoS exploit in openssl (Debian stable only)
1–10 of 10 posts
Re: DoS exploit in openssl (Debian stable only)
#2Re: DoS exploit in openssl (Debian stable only)
#3Re: DoS exploit in openssl (Debian stable only)
#4Re: DoS exploit in openssl (Debian stable only)
#5I don't think this is Debian stable only?
Re: DoS exploit in openssl (Debian stable only)
#6I don't think this is Debian stable only?
Not only does this not seem to mention Debian at all, it links to a redhad bug tracker. Where is the Debian component coming from re the title? Sounds like maybe someone has their hate on for Debian to me.
[0]: https://security-tracker.debian.org/tracker/CVE-2014-0198
Re: DoS exploit in openssl (Debian stable only)
#7Re: DoS exploit in openssl (Debian stable only)
#8I don't think this is Debian stable only?
https://lists.debian.org/debian-security-announce/2014/msg00...
Re: DoS exploit in openssl (Debian stable only)
#9Does anyone know which packages have SSL_MODE_RELEASE_BUFFERS enabled and are vulnerable?
Re: DoS exploit in openssl (Debian stable only)
#10My comment from last time:
Good to note that this was found with KLEE[1]. KLEE is a good for symbolic execution of code and is very cool[2].
This only triggers a crash if you use RELEASE_BUFFERS (not the default) and a warning alert is written when the socket buffer is full. About the only case where a warning alert is generated is when a client attempts a renegotiation without the renegotiation extension (unless insecure renegotiation is allowed by the app). I've not been able to trigger the bug in a test because code generally stops reading once the socket buffer is full so you need the application to exactly fill the socket buffer (so that it doesn't get EAGAIN), then a warning alert can just exceed it.
[1] http://marc.info/?l=openssl-dev&m=139809493725682&w=2 [2] http://klee.github.io/klee/