Assertion failure: !aIID.Equals((::nsISupports::COMTypeInfo<int>::kIID)), at content/svg/content/src/SVGAnimatedRect.cpp:18
Looks like sec-critical. viewBox handling looks very odd.
(but I assume this is a regression from webidlification.)
The code is: 15 NS_INTERFACE_MAP_BEGIN_CYCLE_COLLECTION(SVGAnimatedRect) 16 NS_INTERFACE_MAP_ENTRY(nsISupports) 17 NS_WRAPPERCACHE_INTERFACE_MAP_ENTRY 18 NS_INTERFACE_MAP_END NS_WRAPPERCACHE_INTERFACE_MAP_ENTRY strikes again. See bug 798188. The order of lines 16 and 17 needs to be switched.
Created attachment 750571 [details] [diff] [review] patch Still testing it...
Comment on attachment 750571 [details] [diff] [review] patch r=me, but you need to hg add the test file.
Created attachment 750598 [details] [diff] [review] patch
This can't land without security approval.
Boris, can you help me with this? I just changed the order of 2 lines :)
You just need to request security approval on the patch.
Comment on attachment 750598 [details] [diff] [review] patch [Security approval request comment] How easily could an exploit be constructed based on the patch? I have no idea how to do it. Do comments in the patch, the check-in comment, or tests included in the patch paint a bulls-eye on the security problem? The tests show how to trigger the assert, but I'm not sure how to exploit it. Which older supported branches are affected by this flaw? Aurora 23. If not all supported branches, which bug introduced the flaw? Bug 866796. Do you have backports for the affected branches? If not, how different, hard to create, and risky will they be? This should apply to Aurora 23. How likely is this patch to cause regressions; how much testing does it need? This is a very safe patch.
Comment on attachment 750598 [details] [diff] [review] patch sec-approval+ for m-c. Please prepare an aurora patch and nominate once it is on trunk.
Comment on attachment 750598 [details] [diff] [review] patch [Approval Request Comment] Bug caused by (feature/regressing bug #): 866796 User impact if declined: a crash... Risk to taking this patch (and alternatives if risky): nothing.