User Controls
Depending on the browser, could you force a crash?
-
2021-08-31 at 7:44 AM UTCI know there are some buffer overflow shenanigans in old FF. And while i haven't looked into them yet, i was wondering if you could just write a piece of JS let's say, that basically kills the browser.
other than that any exploits for certain browsers you are familiar with that do the same? -
2021-08-31 at 2:05 PM UTCWith modern browsers, tabs are generally isolated into their own processes (which is why if you look at your process manager you probably see a bazillion processes) so even if you max out your utilization on a page, other browser functions don’t get starved (because they’re different processes and will get scheduled by the os).
If you want to crash the whole browser you either need to manage to break out of the JS sandbox then escape process isolation somehow (not easy) or find an IPC mechanism that’s abusable. Latter is probably easier, with a dozen new browser APIs a year there’s bound to be something that’s not adequately throttled or size capped -
2021-08-31 at 3:21 PM UTCdidn't spamming auto embed YT videos crash browsers
-
2021-09-01 at 2:21 AM UTC
Originally posted by Lanny With modern browsers, tabs are generally isolated into their own processes (which is why if you look at your process manager you probably see a bazillion processes) so even if you max out your utilization on a page, other browser functions don’t get starved (because they’re different processes and will get scheduled by the os).
If you want to crash the whole browser you either need to manage to break out of the JS sandbox then escape process isolation somehow (not easy) or find an IPC mechanism that’s abusable. Latter is probably easier, with a dozen new browser APIs a year there’s bound to be something that’s not adequately throttled or size capped
Could you elaborate a little on IPC, i am vaguely familiar with the term. I might be more familiar with the concept but IPC as a term isn't something i hear too often.
Other than that, the things you mentioned are why i figured i'd make a thread to ask. :\ -
2021-09-01 at 3:28 AM UTCYou could lure them to your webserver and create an IFRAME which sits as an overlay over the scroll bar, so when they go to grab the scrollbar, it won't move, but the IFRAME will, and when they release the IFRAME onto the current browser window, you could run further CODE through the IFRAME.
-
2021-09-01 at 3:34 AM UTC
Originally posted by ⠀⠀⠀⠀⠀⠀ You could lure them to your webserver and create an IFRAME which sits as an overlay over the scroll bar, so when they go to grab the scrollbar, it won't move, but the IFRAME will, and when they release the IFRAME onto the current browser window, you could run further CODE through the IFRAME.
I have considered injecting through iFrames, but there are some secure browsers that will nip that in the bud. -
2021-09-01 at 3:49 AM UTC
-
2021-09-01 at 4:45 AM UTC
-
2021-09-01 at 4:58 AM UTCBrowsers crash on their own, so simply investigate why they do and replicate.
-
2021-09-01 at 5:49 AM UTC
-
2021-09-04 at 2:39 PM UTC
Originally posted by Sophie Could you elaborate a little on IPC, i am vaguely familiar with the term. I might be more familiar with the concept but IPC as a term isn't something i hear too often.
Other than that, the things you mentioned are why i figured i'd make a thread to ask. :\
"Inter-Process Communication", it's just a catchall term for how processes communicate with each other (on the same machine). In a browser's case it's _probably_ domain sockets but IDK. The particular mechanism isn't too important, the central point is that if you want to escape your tab's sandbox you need to exploit not what you can do within the tab's process, but what you can make other shared process do by communicating with them.
Originally posted by ⠀⠀⠀⠀⠀⠀ You could lure them to your webserver and create an IFRAME which sits as an overlay over the scroll bar, so when they go to grab the scrollbar, it won't move, but the IFRAME will, and when they release the IFRAME onto the current browser window, you could run further CODE through the IFRAME.
Retarded. You have no idea what an iframe is as evidenced by you thinking there is any point in instantiating one to run some code when a user is already sitting on your webpage.
Originally posted by ⠀⠀⠀⠀⠀⠀ Obfuscate the IFRAME injection with HEX maybe.
Further proof of retardation. "durrr, hide it with 1337speak HEX like a HAXOR does". You're like a child that sees adults do things and tries to mimic how they look without even the most basic understanding of what the point is. -
2021-09-04 at 2:44 PM UTC
Originally posted by Lanny "Inter-Process Communication", it's just a catchall term for how processes communicate with each other (on the same machine). In a browser's case it's _probably_ domain sockets but IDK. The particular mechanism isn't too important, the central point is that if you want to escape your tab's sandbox you need to exploit not what you can do within the tab's process, but what you can make other shared process do by communicating with them.
Retarded. You have no idea what an iframe is as evidenced by you thinking there is any point in instantiating one to run some code when a user is already sitting on your webpage.
Further proof of retardation. "durrr, hide it with 1337speak HEX like a HAXOR does". You're like a child that sees adults do things and tries to mimic how they look without even the most basic understanding of what the point is.
That didn't scare me. -
2021-09-04 at 10:59 PM UTCOk, what if you hacked into the router and disabled the firewall and set it to passthrough and then used a port scanner to find out what ports the browser was running on and then flooded the ports with requests? That would at least freeze up the browser.
-
2021-09-04 at 11:30 PM UTC
-
2021-09-05 at 2:33 AM UTC
-
2021-09-05 at 2:54 AM UTC
-
2021-09-05 at 2:57 AM UTC
Originally posted by vindicktive vinny off topic but do you fingerprinting our browsers ?
if not why cant images be uploaded without fingerprinting enabled.
If you're concerned with browser fingerprints you need to change your headers, disable javascript and get a HTML5 Canvas blocker.
Or just use Tor. -
2021-09-05 at 11:49 AM UTC
-
2021-09-05 at 3:56 PM UTC
-
2021-09-05 at 3:58 PM UTC
Originally posted by Lanny No and I’m not sure what “fingerprinting enabled” means. The only place you can upload images on the site is avatars.
theres an option in mozilla browser to enable or disable this "fingerprinting" thing.
and yes, theres a reason my avatar is blank after you deleted my avatar until now.
