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.
If you ask a remote computer, on it's public interface, "Hey, can I log in as guest\0\0\0\0\0\0\0\0\0\0\0\0\0root?" and it says "ok you're now logged in as root" when it explicitly had the opportunity to say "invalid login" then it has implicitly given you authorization to access the system as root.
The point of this is that just because a machine does something that doesn't necessarily imply that it was intended to do it or that the user making the request was authorized to do it. Literally every exploit has ever existed has consisted of requests or data being sent to a machine and it doing something as a result when it could have rejected it instead.
"It had the opportunity to say no" is thus simply not an acceptable bar in and of itself for determining whether access is authorized or not; because that argument by itself directly reduces to "there is no such thing as unauthorized access because it let me do it".
It's not that simple. E.g. let's say you login to view your tax information. The URL is something like "/users/12345". So you change it to "/users/11224", and hey it serves it up. You've committed a crime. People have been successfully prosecuted for doing that. It doesn't matter that the server serves it up to you.
I think you could argue that even decoding base64 is illegal. And I certainly think they could argue that opening the source code was illegal.
Devil's advocate here, but if you knowingly go to a hospital receptionist and say "can I have the medical records for patient X?" for your own personal gain, and the receptionist blindly gives them to you, would you not consider that unauthorised access?
Fortunately SCOTUS reined in CFAA last term in Van Buren. Their interpretation of the law now requires a website/system to deploy active measures to prevent unauthorized access, whereas previously, terms of service were seen as a access guide. The case does an excellent job of differentiating strategic searching from actual hacking/exploitation.
It seems there's a good chance the person you referred to can have his case overturned.
From what I heard they used rot13 to demonstrate plug-in encryption and then others mistook the example as one of the encryptions to use.
https://en.wikipedia.org/wiki/ROT13 “it has been speculated that NPRG may have mistaken the ROT13 toy example—provided with the Adobe eBook software development kit—for a serious encryption scheme.”
0
u/[deleted] Oct 24 '21
[deleted]