Re:Null pointer dereference – new security bug for OpenSSL
by duked on Thursday May 01, 2014 @08:52PM
(#7683567)
KLEE is ok on small programs but has a lot of limitation with real world programs (using libraries mostly) at least according to a USENIX paper last year: https://www.usenix.org/conference/cset13/workshop-program/pr...
Re:Null pointer dereference – new security bug for OpenSSL
by munin on Thursday May 01, 2014 @10:28PM
(#7683869)
How does what you say square with the evidence that klee found a bug in OpenSSL which is about as real world as it gets?
Re:Null pointer dereference – new security bug for OpenSSL
by jevinskie on Thursday May 01, 2014 @08:21PM
(#7683466)
KLEE is very interesting! I am looking into it for improving tests on some of my company's small-but-tricky functions.
Here is an example of its power and how to use it: http://feliam.wordpress.com/2010/10/07/the-symbolic-maze/
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/