4 ms·
From this twitter thread: https://twitter.com/mikko/status/1224349151384821762 https://twitter.com/mikko/status/1224349151384821762 You can't search traceroute
by kusha 7y ago
From this twitter thread: https://twitter.com/mikko/status/1224349151384821762 https://twitter.com/mikko/status/1224349151384821762
You can't search traceroute. Weird.
- ryanlol 7y agoNot weird, just WAF.
- XMPPwocky 7y agoYou also can't search alert(1), so probably just a silly WAF.
- rahuldottech 7y agoOr for `<script>`
- batuhanicoz 7y agoPeople on that thread also noticed more keywords and think it might be Akamai WAF. I don't know enough about it be sure. You can't have some strings in the URL for the main NSA.gov domain as well. So https://nsa.gov/fakething?hey=traceroute https://nsa.gov/fakething?hey=traceroute will give you the same error.
- ehsankia 7y agoYeah it's clear that a system is just blindly grepping the request url for certain keywords and killing the query.
- deleted 7y ago[deleted]
- mythz 7y agoSo you can't search for `traceroute` or `tracert` directly but you can search for misspelling like `tracerout` and the results page just ends up showing the search results for `traceroute` so it's not exactly a very sophisticated filter.
- jaywalk 7y agoWell the purpose of the filter is almost certainly to prevent running the command on the server in case of an attack, not to prevent it from being searched on Google. You'd have to spell it correctly to get the server to execute it.