3 ms·
"Poking and prodding" can get them in legal hot water. I understand (and please correct me if I am wrong) Only NSA legally, are allowed to "poke and prod sites"
by rdtsc 13y ago
"Poking and prodding" can get them in legal hot water. I understand (and please correct me if I am wrong) Only NSA legally, are allowed to "poke and prod sites". Well, and I guess by legally you can interpret that as "they are legally allowed to" or "nobody is really prepared to tell them no".
Anyway, a lot of anti-hacking laws are written that "poking and prodding is not benign" admitting to too many details of that on national media might be a case of bad judgement.
- ams6110 13y agoGet who in hot water? The botnets that continually, around the clock 365 days a year "poke and prod" nearly every IP address that responds to port 80 or 443?
- rdtsc 13y agoDavid Kennedy, they guy who just admitted it on TV? > The botnets that continually, around the clock 365 days a year "poke and prod" nearly every IP address that responds to port 80 or 443? If you can find an operator that confesses it publicly. How many do it? Pretty sure if say Vasile Bogdan from Bucharest, calling CNN confessing he just broke into Bank of America CC processing center, he might find himself on Interpol's most wanted list.
- theboss 13y agoYou are very wrong. Poking and proding is completely legal and isn't going to send anyone to jail. He's not performing a full pen-test on the site. He's not looking to get a shell. He's just checking out best practices. Is there an HSTS header? Is my input validated? etcetc. The main hacking law that applies here is the CFAA and Dave definitely isn't violating it. To violate it you have to access something you're not allowed to. Nobody will EVER go to jail for an XSS or the types of things he's poking around for. This is because the computer the code is running on is his own....
- tptacek 13y agoReflected XSS testing can easily end up disrupting the whole site for every user; all it takes is for input to some endpoint to get stored and replayed across the site. Relying on the idea that any kind of active testing against a site you don't own is safe, technically or legally, is a bad idea.
- theboss 13y agoReflected XSS? Do you mean stored? If Dave is testing for reflected XSS he's going to be alert(1)'ing or using img tag....Which is not a persistent xss... For reflected xss to affect every user on the site he's going to have to use his own toolkit to send a malicious link to every user on the site....
- tptacek 13y agoI mean reflected. The kind you don't expect to get stored. If that's a surprise to you, you might not test a lot of websites, because this comes up somewhat regularly. By the way, the XSS payload has nothing to do with the persistence of the attack. You alert() stored XSS in testing too.
- theboss 13y agoI do test a lot of websites actually but I mis-understood what you meant. Like the other guy said this area is grey. If he accidentally finds a stored xss of the magnitude you suggest I'm 100% sure he still wouldn't go to jail. Who tests with a malicious payload? There would be no malicious intent in the situation and no unauthorized access...still.
- tptacek 13y agoYou didn't say this was a grey area. You said "Nobody will EVER go to jail for an XSS" and then cited the CFAA as evidence of that fact, suggesting that you might have some minor gaps on how XSS works and that you definitely have major gaps on how CFAA works. Pro-tip: avoid stringing "Nobody will EVER go to jail for" and "CFAA" together in the same paragraph.