Re:Firefox Under Fire: Anatomy of latest 0-day attack
by pjtr on Wednesday August 12, 2015 @01:25AM
(#10046170)
Can anyone explain what the bug was?
[ Parent
| on HN ]
Re:Firefox Under Fire: Anatomy of latest 0-day attack
by mbrubeck on Wednesday August 12, 2015 @01:41AM
(#10046218)
This previous thread has links to more detail: https://news.ycombinator.com/item?id=10021376
Re:Firefox Under Fire: Anatomy of latest 0-day attack
by pjtr on Wednesday August 12, 2015 @01:54AM
(#10046259)
But none that describe the cause of the bug, right?
Re:Firefox Under Fire: Anatomy of latest 0-day attack
by digitalzombie on Wednesday August 12, 2015 @05:27AM
(#10046874)
Well, the person who reported the bug comment in depth details of what it does from his point of view on that link.
So yes?
ctrl+f to find user "fukusa" and you'll find that one of his/her comment goes into depth.
Re:Firefox Under Fire: Anatomy of latest 0-day attack
by fukusa on Wednesday August 12, 2015 @06:51AM
(#10047075)
Thanks, also have a look at: https://news.ycombinator.com/item?id=10047010
Re:Firefox Under Fire: Anatomy of latest 0-day attack
by pjtr on Thursday August 13, 2015 @01:31AM
(#10052413)
Thanks, that's closer to what I was looking for. I'm still a bit unclear on what exactly the root cause of the bug is. A flawed plugin API (PlayPreview), flawed usage of that API, a bug in the implementation of that API, a combination of these or something else. From your link it looks like the plugin now does not use the API anymore, but the API still exists. But the API implementation seems to have required fixes as well. [1] [2]
[1] https://github.com/mozilla/gecko-dev/commit/2e67509c8a3cefe8...
[2] https://github.com/mozilla/gecko-dev/commit/8b7f7bde8f21bd71...