Bugzilla@Mozilla – Bug 453526
Remaining attack vectors in feed preview on 1.8 branch
Last modified: 2008-12-16 16:57:19 PST
Summon comment box
See bug 360529 comment 68 and bug 360529 comment 69.
------- Comment #68 From moz_bug_r_a4@yahoo.com 2008-09-03 05:11:44 PDT There are two oversight. fx2.0.0.17 is still exploitable. http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/components/feeds/src/FeedWriter.js&rev=1.2.2.36&mark=635#623 This is exploitable. I'll attach a testcase. http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/components/feeds/src/FeedWriter.js&rev=1.2.2.36&mark=404,406#397 I think this is unsafe. But, I cannot create a testcase since I don't know a way to execute this catch block. ------- Comment #69 From moz_bug_r_a4@yahoo.com 2008-09-03 05:14:55 PDT (-) Created an attachment (id=336641) [attachment 336713 [details] in this bug --dveditz] testcase 9 - handlers[0].doCommand() This works on fx2.0.0.17-candidate-build2 (2008082909). This uses bug 451680's XSS trick.
Mano, any update here?
Mano, have you had time to work on this? I'd hate to miss this for a third release in a row, especially since it's the last Firefox 2 release...
Mano, please attach a 1.8 patch for this. Code freeze is on Monday.
Created attachment 348427 [details] [review] patch See bug 388207, I didn't remove the element from subscribe.xhtml for the sake of backwards-compatibly.
Comment on attachment 348427 [details] [review] patch Looks good.
Comment on attachment 348427 [details] [review] patch Approved for 1.8.1.19, a=dveditz for release-drivers
Can we get this landed asap? Code freeze was technically last night...
Checking in browser/components/feeds/src/FeedWriter.js; /cvsroot/mozilla/browser/components/feeds/src/FeedWriter.js,v <-- FeedWriter.js new revision: 1.2.2.37; previous revision: 1.2.2.36 done
Verified with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19pre) Gecko/2008112503 BonEcho/2.0.0.19pre.
not an issue on 1.8.0