Closed Bug 448166 Opened 16 years ago Closed 16 years ago

escaped low surrogates possible XSS hazard in URIs

Categories

(Core :: Networking, defect)

1.8 Branch
defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: dveditz, Assigned: bzbarsky)

References

(Blocks 1 open bug, )

Details

(Keywords: verified1.8.1.17, Whiteboard: [sg:low])

On "The Scanner" blog Gareth noticed that html-escaped low surrogates in javascript uris were ignored as if they weren't there, a possible XSS hazard if sites don't recognize javascript: links.

http://www.thespanner.co.uk/2008/06/30/javascript-protocol-fuzz-results/

This works in the latest Firefox 2.0.0.16 but not Firefox 3. The trunk did get a fix for bug 316394 but that's in CSS and wouldn't have fixed this I don't think. Putting escaped low surrogates into HTML elements correctly leads to unknown tags (e.g. <scr&#xdc00;ipt> doesn't work).

<a href="http://www.moz&#xdc00;illa.com">shouldn't be mozilla</a>
Whiteboard: [sg:low]
Bug 316394 covered both CSS escapes and HTML numeric entities.
Blocks: xss
Depends on: 316394
Flags: blocking1.8.1.17+
Assignee: nobody → bzbarsky
This has now been posted to a higher profile site (microsoft)
http://blogs.technet.com/bluehat/archive/2008/08/14/targeted-fuzzing.aspx
The branch merge for bug 316394 fixes this testcase.
Flags: in-testsuite?
Fixed by backporting bug 316394.

I checked in an HTML test for this.  We can use bug 316394 to track the xpcom unit tests needed here.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: in-testsuite? → in-testsuite+
Resolution: --- → FIXED
Keywords: fixed1.8.1.17
Verified FIXED using : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/2008082909 Firefox/2.0.0.17, which yields http://www.moz�illa.com/.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/2008070205 Firefox/2.0.0.16, however, has http://www.mozilla.com.

Replacing fixed1.8.1.17 keyword with verified1.8.1.17; additionally, since this bug seems scoped to the 1.8 branch, marking its state as VERIFIED FIXED.
Status: RESOLVED → VERIFIED
Group: core-security
You need to log in before you can comment on or make changes to this bug.