Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

JS DoS #87

Closed
jumde opened this issue Jul 12, 2018 · 8 comments
Closed

JS DoS #87

jumde opened this issue Jul 12, 2018 · 8 comments

Comments

@jumde
Copy link
Contributor

jumde commented Jul 12, 2018

<script>
   while(true) {
     alert(1);
   }
</script>

Test Plan

  • please see PR
@jhreis jhreis added this to the Backlog milestone Jul 17, 2018
@tmancey tmancey removed this from the Backlog milestone Aug 11, 2018
@tmancey
Copy link
Collaborator

tmancey commented Aug 30, 2018

@jumde hi, you classified this issue as a bug, then removed bug. Can you please let me know if this is a bug or an enhancement as I am making sure all tickets are correctly labeled to help with reporting?

@tmancey tmancey added the blocked: needs info Needs further information before work can commence label Aug 30, 2018
@jumde
Copy link
Contributor Author

jumde commented Aug 30, 2018

label bug sounds good.

@jumde jumde added the bug label Aug 30, 2018
@tmancey tmancey added the blocked If a ticket is blocked for some reason, if not using a sub-block label, please provide info in issue label Sep 5, 2018
@tmancey tmancey removed blocked If a ticket is blocked for some reason, if not using a sub-block label, please provide info in issue blocked: needs info Needs further information before work can commence labels Oct 2, 2018
@danishjafri88 danishjafri88 self-assigned this Nov 27, 2018
@danishjafri88
Copy link
Contributor

danishjafri88 commented Nov 28, 2018

The app is susceptible to js DOS attack especially the window.alert attack. The alert shown blocks the entire screen.
For other bowsers following is the result:
FF: same as brave
Safari: custom alert component
img_6069
Chrome: Blocking alert with option to suppress window.alert after multiple alerts are thrown
img_6067
img_6068

Possible solutions for this DOS attack is either of Chrome's or Safari's way.

@jamesmudgett
Copy link
Contributor

@danishjafri88 We need a way to suppress, the Chrome flow works well.

@srirambv
Copy link
Contributor

srirambv commented Sep 5, 2019

Verification passed on iPhone XR with iOS 13 running 1.12(19.09.04.23)

  • Verified app doesn't hang when constant popups show up
  • Verified selecting Ok or Cancel doesn't cause app to hang
  • Verified Suppress notifications only affect for that particular session and doesn't show up again until the tab is closed and reopened

Verification PASSED on iPad Air 3rd Generation iOS 13.1 running 1.12 (19.09.10.18):

  • Verified app doesn't hang when constant popups show up
  • Verified selecting Ok or Cancel doesn't cause app to hang
  • Verified Suppress notifications only affect for that particular session and doesn't show up again until the tab is closed and reopened

@kjozwiak
Copy link
Member

@danishjafri88 quick question regarding this fix. Whenever you suppress the modal/dialog/alerts, the page becomes unresponsive. Example:

Is the above expected? Or should the page recover once you suppress the alerts?

@srirambv
Copy link
Contributor

@kjozwiak that expected. More discussion on this here: https://bravesoftware.slack.com/archives/C06UXF3KJ/p1567691573119300

@srirambv
Copy link
Contributor

Verification passed on iPhone 7+ with iOS 12.4.1 running 1.12(19.09.13.06)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants