Closed Bug 1422590 Opened 8 years ago Closed 8 years ago

xss on the site qsurvey.mozilla.com

Categories

(Websites :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ignatio2007, Unassigned)

References

()

Details

(Keywords: reporter-external, Whiteboard: [reporter-external] [web-bounty-form] [verif?])

how to reproduce: 1. navigate to url: http://qsurvey.mozilla.com/s3/?__slug=www.surveygizmo.com/s3/4039568/123 2. will be show a popup alert with name of domain
Flags: sec-bounty?
Thanks Sergey. I can validate this bug. Ally, this looks very similar to a bug reported a month ago, and was later fixed by SG (bug 1414696). Can you please have the SG team look into this instance as well? Ideally, we would like to see a root cause fix, rather than fixing individual vulnerability instances.
Flags: needinfo?(allysa.netzel)
See Also: → 1414696
Ally: further more, this appears to be systemic and fixes do not appear to be fixing the core issue, can the SurveyGizmo team please address that specific concern in your response?
Hi All - I have passed this information along and will update when I know more. Thank you!
Flags: needinfo?(allysa.netzel)
Ally – is there any way for Mozilla to add specific HTTP headers to our domain (qsurvey.mozilla.com)?
Flags: needinfo?(allysa.netzel)
Hi April - Could you please explain why you need this and what you are trying to do please so I may pass this information along as well? Thank you!
Flags: needinfo?(allysa.netzel)
We have had a *lot* of XSS bugs on qsurvey, at least a dozen or so by now. If we could set our own Content-Security-Policy (CSP) header on our domain, it would go a long way towards at least stopping the bad effects of all these XSS vulnerabilities in qsurvey.
A release fixing this bug went live today! I also heard that Jaime is working with you to get the header you want set up.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Flags: sec-bounty? → sec-bounty+
Group: websites-security
You need to log in before you can comment on or make changes to this bug.