Closed
Bug 1436485
Opened 8 years ago
Closed 4 years ago
Cross Site XSS ( Cross Site Scripting ) at Firefox Focus for Android
Categories
(Focus :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1739934
People
(Reporter: u608619, Unassigned)
Details
(Keywords: reporter-external, sec-low, wsec-selfxss, Whiteboard: [not fennec])
Attachments
(1 file)
|
168.34 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Steps to reproduce:
Hello Mozilla Security Team,
I downloaded the Firefox Focus app from Google Play. -> Latest version. I turned on the Firefox Focus application. I wrote javascript: alert ('ismailtasdelen') javascript payload in the search section. And I did the search. I printed my name on the screen of the mobile app.
Mobile App : Firefox Focus
Mobile App Version : Last version.
Phone & Device Model : Nokia 6
Device OS : Android
OS Version : Android 8.0 Oreo
XSS Payload : Javascript:alert('ismailtasdelen')
Actual results:
I could run XSS Payload.
Expected results:
I could successfully execute the Javascript code (:
Comment 1•8 years ago
|
||
How are you handling Focus security bugs? This does not belong in Firefox for Android.
Flags: needinfo?(sdaswani)
Mobile apps running on IOS and Android platform are running my xss payload.
Whiteboard: [not fennec]
Can someone from the sec team give us a security severity on this - sec low, moderate, or high?
Flags: needinfo?(sdaswani) → needinfo?(fbraun)
I wanted to let you know that I found a low level xss security vulnerability ((:
Comment 6•8 years ago
|
||
Thank you for reporting this bug to us.
I understand this is a self-xss. The user has to type in the attacking code themselves.
Rating sec-low according to our ratings at <https://wiki.mozilla.org/Security_Severity_Ratings>
Also, the code seems to be running at low privileges (e.g., location.href == "about:blank).
Note that the URL is case-sensitive. "javascript:alert(1)" in the URL bar does not seem to work, but "Javascript:alert(1)" (uppercase) does.
If we have any checks that are supposed to stop those kind of things, we should ensure them being case-insensitive.
Flags: needinfo?(fbraun)
Keywords: sec-low,
wsec-selfxss
(In reply to Frederik Braun [:freddyb] from comment #6)
> Thank you for reporting this bug to us.
>
> I understand this is a self-xss. The user has to type in the attacking code
> themselves.
> Rating sec-low according to our ratings at
> <https://wiki.mozilla.org/Security_Severity_Ratings>
> Also, the code seems to be running at low privileges (e.g., location.href ==
> "about:blank).
>
> Note that the URL is case-sensitive. "javascript:alert(1)" in the URL bar
> does not seem to work, but "Javascript:alert(1)" (uppercase) does.
> If we have any checks that are supposed to stop those kind of things, we
> should ensure them being case-insensitive.
Thanks for the security ranking Frederik!
https://www.mozilla.org/en-US/security/bug-bounty/hall-of-fame/ --> I am delighted if you add my name to the report I am reporting. More important than the gift from the money for me (:
Thanks
Hey, what's the latest situation? The report has not been finalized and is still not fixed. I would also like to add it to the Hall of Fame list.
Comment 10•8 years ago
|
||
Daniel - can you advise on 1) security rating - low medium high and 2) hall of fame?
Thanks!
Flags: needinfo?(dveditz)
| Reporter | ||
Comment 11•8 years ago
|
||
Hello,
XSS weaknesses are considered as medium.
Hall of Fame https://www.mozilla.org/en-US/security/bug-bounty/hall-of-fame/
İsmail Taşdelen
Thanks (:
| Reporter | ||
Comment 12•8 years ago
|
||
Hello,
I did not say my social media account.
İsmail Taşdelen - https://www.linkedin.com/in/ismailtasdelen/
If there is a character problem at the end, you can write it as "Ismail Tasdelen".
Thanks
Comment 13•8 years ago
|
||
This has already been rated sec-low as it requires the attacker to convince the user to type or paste the code into the address bar of Focus Android.
As I understand the security HOF is for researchers that received awards for sec-high or sec-critical bugs as outlined in https://www.mozilla.org/en-US/security/bug-bounty/faq/#eligible-bugs Leaving the NI to Dan to confirm this.
Comment 14•8 years ago
|
||
(In reply to Kevin Brosnan [:kbrosnan] from comment #13)
> This has already been rated sec-low as it requires the attacker to convince
> the user to type or paste the code into the address bar of Focus Android.
>
> As I understand the security HOF is for researchers that received awards for
> sec-high or sec-critical bugs as outlined in
> https://www.mozilla.org/en-US/security/bug-bounty/faq/#eligible-bugs Leaving
> the NI to Dan to confirm this.
Thanks Kevin. I also am facepalming for not reading the sec-low rating! :/
Comment 15•8 years ago
|
||
Flagging for the bounty committee per comment 8.
So far the client security Hall of Fame has included only people who were awarded bounties (sec-low are usually not eligible). The Web hall of fame _does_ include people who have found valid issues but weren't awarded a bounty -- it depends on the site involved.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(dveditz) → sec-bounty?
Summary: Cross Site XSS ( Cross Site Scripting ) at Firefox Focus → Cross Site XSS ( Cross Site Scripting ) at Firefox Focus for Android
| Reporter | ||
Comment 16•8 years ago
|
||
If you recieve a return, then you can close the report.
Updated•8 years ago
|
Component: General → Security: Android
Product: Firefox for Android → Focus
Version: unspecified → 4.0
| Reporter | ||
Comment 17•8 years ago
|
||
Yes
Updated•7 years ago
|
Group: firefox-core-security
Flags: sec-bounty? → sec-bounty-
Comment 18•7 years ago
|
||
Emily another security bug you can take a stab at.
Assignee: nobody → ekager
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Assignee: ekager → nobody
Updated•3 years ago
|
Component: Security: Android → General
Updated•2 years ago
|
Keywords: reporter-external
You need to log in
before you can comment on or make changes to this bug.
Description
•