During my research and testing of new IDS (Intrusion Detection System)
like Suricata, I’ve
found a Stored Cross-site Scripting (XSS) vulnerability in Snorby (that
I’d like to use…
I played around with the code to see if can change it to avoid using the
fork bomb. Here’s what I came up with https://gist.github.com/ptantiku/d37c364cd13bb31a1ee6
It seems to need at least 500 threads to update the URL at 5ms for this to
work (tested on Chrome x64 43.0.2357.130, Linux, locally).
And the first setInterval() can be substituted for setTimeout(…,10) which
will run only once for waiting the pop-up window to open.
Can you perform any actions on the page once the URL is replaced, or is it
non responsive? (asking because PoC did not work on my Chrome 43.0.2357.130
(64-bit) on OSX). If it is non responsive then the impact is very limited.
Worst thing I can think of is showing “your account is suspended, please
contact technical support on 0800-555-555″ and then using the trust user
puts in the URL for phone phishing. If it is responsive, then…
I think they called it DOS because the chrome.exe process starts to consume
system memory out of control.
In my example (Win7 Chrome 43.0.2357.130) it ended up consuming 4GB+ of
memory before it finally gave up 3 minutes or so later and issued an error
message in both windows.
Potentially, with multiple such frames being launched one could make it
crash.
That’s beside the point though as the URL spoofing is clearly there.