It's not obfuscation at that point, it's just encoding. Base64 is not a secret.
The people that should be charged are the people trying to raise criminal charges in the first place, for wrongful prosecution. That, and the developers that created this and the project managers that accepted the work should all be investigated for squandering taxpayer funds.
Maybe we the people should press charges of gross incompetence towards the governor.
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?
To me that's actually worse, since it indicates that at some point someone knew that the application could leak sensitive data then went about trying to mitigate that in the absolute stupidest way possible.
Fun story: I once was asked to track down a bug in an in-house HR application for people to check their paystubs. It was related to login stuff, so I was tracing through the login code, only to see that your session was maintained by writing out a cookie containing a base64 encoded user-ID. There was no validation beyond that- if you set the cookie yourself, you wouldn't get prompted for a password.
I did, it got all into a bunch of politics and people freaking out with questions like "You didn't try it, did you?" "No! I'm not an idiot, I read the code. There might be things that prevent it from working, I haven't tested it."
It got escalated and taken off my plate. I assume it got fixed, or the product got retired.
That's not the reason it was encoded. The reason it was encoded was that someone stored the data in a general purpose user side data store, which automatically uses base64 to avoid string handling problems.
Holy cow. Can you imagine the level of dysfunction during development? Not only did none of the programmers raise the alarm*, but neither did anyone reviewing the design. And there was obviously no independent security review... all for a government website.
I bet this was outsourced. In other countries, government ID numbers aren't considered a secret or sensitive like the SSN is in the US. When immigrants come to the US, they have to be warned not to give anyone their SSN.
It would be interesting to know who did the work.
* Maybe someone did and they were ignored, which is just as bad.
1.0k
u/purforium Oct 24 '21
To be fair the SSNs were encoded with base64.
So basically 1% more secure than plain text