Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no way to recover from audioworklet hang #15

Open
SArpnt opened this issue Nov 5, 2021 · 4 comments
Open

no way to recover from audioworklet hang #15

SArpnt opened this issue Nov 5, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@SArpnt
Copy link
Contributor

SArpnt commented Nov 5, 2021

by just using the code (_=>{for(;;);})() the website is rendered completely unusable, and the hang is completely undetected.
refreshing doesn't work properly either, the browser (at least my browser) gets stuck, so the only way i can deal with the issue is completely closing the tab.

@SthephanShinkufag SthephanShinkufag added the bug Something isn't working label Dec 6, 2021
@inyourface34456
Copy link

I think this is the shellshock vulnerability, this is a recnoized bug. How did you use it though? What OS are you running (if so, you better catch it)? What browser are you running and when was it last updated? If it has been a while, then you should definitely update, as this is a very extreme security vulnerability, as it can run any code, weather you like it or not.

@ghost
Copy link

ghost commented Jan 6, 2022

Expressions

(_=>{for();})()

SyntaxError: expected expression, got ')'

for()

SyntaxError: expected expression, got keyword 'for'

System

  • Mozilla Firefox 95.0.2 (64-bit)
  • Microsoft Windows NT 6.1 (64-bit)

@SthephanShinkufag
Copy link
Owner

@Diicorp95

(_=>{for(i=1;i;);})()

Also, It's impossible to get a link with it from site.

For example, here link for working code (_=>{for(i=0;i;);})():
https://dollchan.net/bytebeat/#v3b64q1ZKzk9JVbJS0oi3tatOyy/SyLQ1sM601rSu1dTQVKoFAA==

The player will immediately enter an endless loop as soon as you edit 0 to 1 by releasing the key, without giving an updated link.
So you won't be able to share links with broken code.

Of cource, unless you can compose such a link yourself, using decodeURIComponent through the console, for example.

@SArpnt
Copy link
Contributor Author

SArpnt commented Jan 8, 2022

I think this is the shellshock vulnerability, this is a recnoized bug. How did you use it though? What OS are you running (if so, you better catch it)? What browser are you running and when was it last updated? If it has been a while, then you should definitely update, as this is a very extreme security vulnerability, as it can run any code, weather you like it or not.

this has literally nothing to do with shellshock and isn't a security vulnerability, it's a minor issue with the website and has nothing to do with my pc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants