Closed
Bug 1294409
Opened 9 years ago
Closed 5 years ago
Mozilla's "Protect the Fox" page reports "Oh Noes! An error occurred"
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: bsperan, Unassigned)
References
()
Details
Attachments
(1 file)
3.13 KB,
application/javascript
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0.1 Waterfox/47.0.1
Build ID: 20160705170440
Steps to reproduce:
Steps to reproduce:
I filled out this page, like it asks:
https://www.mozilla.org/en-US/about/legal/fraud-report/
The catch is to add an attachment to the "Attachment" area, then type something in the description. In my case, I reported this malware site:
https://aihavscambieuropei.org/4291264200212/46b97a0db466311332456639b71444fe.html
And I tried to attach the firefox-patch.js script the above malware site generated.
Actual results:
Actual page result:
"Oh Noes!
An error occurred. Try back later!"
Expected results:
https://www.mozilla.org/en-US/about/legal/fraud-report/?submitted=True
"Fraud Report
Your report has been sent.
Thank you for your help. It’s our community that makes us great."
DO NOTE: The difference, what made my second attempt successful, was the fact that I left out the "firefox-patch.js" script from the Attachment area, leaving it without an attachment and without an attachment description.
Attached is the script (likely malware) which caused the page to fail. I suspect that there may be something wrong with the aforementioned fraud reporting page's code that handles attachments.
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86_64
Updated•6 years ago
|
Assignee: mitchell → nobody
Component: Miscellaneous → Pages & Content
Product: mozilla.org → www.mozilla.org
Version: other → Production
Comment 1•5 years ago
|
||
Only image files may be uploaded/submitted in this intake form. Closing as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•