3 ms·
I don't know my way around Firefox's source control at all, but I tried to do some digging. My first thought was to look through the changelogs on recent releas
by wlesieutre 7y ago
I don't know my way around Firefox's source control at all, but I tried to do some digging. My first thought was to look through the changelogs on recent release tags, but there's no mention of the CVE that I can find in any of them.
I did find these changes in 72 which look related to the bug:
https://hg.mozilla.org/releases/mozilla-release/rev/8260da04c9b13f7c0e9cc6984a75e689b5fcb8c8 https://hg.mozilla.org/releases/mozilla-release/rev/8260da04...
And poking at one of those referenced files in the beta channel looks like it has the same changes:
https://hg.mozilla.org/releases/mozilla-beta/file/tip/js/src/jit/MIR.h https://hg.mozilla.org/releases/mozilla-beta/file/tip/js/src...
So I think we're good on beta channel?
- dblohm7 7y agoEven security fixes run the Nightly -> Beta -> Release gauntlet, so yes, Beta is fixed.