But you remember the bug, right?
-
-
Replying to @yuhong2
I'm not able to see the bug. Sorry; what was the title?
@JustRogDigiTec1 reply 0 retweets 0 likes -
Replying to @jonathansampson @JustRogDigiTec
I think
@ericlaw saw it too.1 reply 0 retweets 0 likes -
Replying to @yuhong2 @jonathansampson and
Yuhong Bao Retweeted Eric Lawrence 🎻
As another clue:https://twitter.com/ericlaw/status/626092588550893568 …
Yuhong Bao added,
2 replies 0 retweets 0 likes -
Incidentally, Jonathan, Justin, and Eric no longer work for Microsoft. :)
1 reply 0 retweets 1 like -
But I am assuming that at lease some of them still remember what it was.
2 replies 0 retweets 0 likes -
Replying to @yuhong2
I might remember a title; but
@berendjanwever's bugs are pretty wild, so I doubt I'd recall specifics
@ericlaw@JustRogDigiTec1 reply 0 retweets 0 likes -
Replying to @jonathansampson @berendjanwever and
So do anyone remember whether it was considered exploitable?
1 reply 0 retweets 0 likes -
Replying to @yuhong2 @jonathansampson and
If it was a guaranteed null it is not exploitable but the challenge is proving this.
2 replies 0 retweets 0 likes -
Replying to @JustRogDigiTec @jonathansampson and
Yea, that is what I am asking.
1 reply 0 retweets 0 likes
Seriously? It's like 2 seconds in a debugger to detect this is a hard coded NULL pointer
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.