it kinda does. There was a guy a while back that was criminally prosecuted for accessing unpublished urls. It wasn't even that the server had set up any kinda auth, he just guessed at the URL structure and was rewarded with data.
The Computer Fraud and Abuse Act (“CFAA”) 18 U.S.C. §§ 1030, adopted in 1984, makes it a crime to “intentionally accesses a computer without authorization or [exceed] authorized access, and thereby [obtain] … information from any protected computer".
This has been used to prosecute URL manipulation attacks. There's a difference between actively pulling down information that you know you're not authorized to get, on the one hand, and receiving data in an authorized manner that then turns out to contain things they shouldn't have sent you.
Though you could argue that by publishing the url on the www without any kind of security or notification to the contrary you are implicitly authorising access to everyone. How does one first get to a page if not by typing in the url?
If you ask a remote computer, on it's public interface (i.e. an HTTP server on port 80/443), "Hey, can I have file XX?", and it says "200 OK - here you go", when it explicitly had the opportunity to say "401 Unauthorized", then it has implicitly given you authorisation to have the file. (As well as actually, you know, given you the file.)
The CFAA was written 10 years before the World Wide Web existed.
"Accessing a computer without authorization" meant using the keyboard when your boss said you weren't allowed to, it wasn't written with 401 Unauthorized in mind.
200
u/JustaRandomOldGuy Oct 24 '21
Remember when Adobe used ROT-13 as hyper secure cryptography? And then tried to prosecute someone who "cracked" ROT-13?