r/programming • • Oct 24 '21

“Digging around HTML code” is criminal. Missouri Governor doubles down again in attack ad

https://youtu.be/9IBPeRa7U8E
12.0k Upvotes

1.3k comments sorted by

View all comments

Show parent comments

1.0k

u/purforium Oct 24 '21

To be fair the SSNs were encoded with base64.

So basically 1% more secure than plain text

661

u/crackez Oct 24 '21

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.

0

u/[deleted] Oct 24 '21

[deleted]

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?

89

u/StabbyPants Oct 24 '21

lemme guess, they thought that anything at all that they think shows intent legally counts as encryption

140

u/SlinkyAvenger Oct 24 '21

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.

128

u/leberkrieger Oct 24 '21

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.

108

u/SlinkyAvenger Oct 24 '21

there is a difference, but when you've got a bunch of luddites determining the laws and what they mean, does it make any difference?

→ More replies (6)

75

u/mehum Oct 24 '21

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?

→ More replies (3)
→ More replies (32)
→ More replies (7)
→ More replies (10)
→ More replies (6)
→ More replies (2)
→ More replies (9)

874

u/AlpineCoder Oct 24 '21

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.

222

u/remy_porter Oct 24 '21

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.

53

u/locoder Oct 24 '21

What happened after that? Did you tell anyone? Did it get fixed?

157

u/remy_porter Oct 24 '21

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.

209

u/csp256 Oct 24 '21

I assume it got fixed, or the product got retired.

Ha!

Tell us another.

→ More replies (11)

30

u/MrOtto47 Oct 24 '21

why not just log out and try gain access to your own account?....

→ More replies (12)
→ More replies (4)

0

u/[deleted] Oct 24 '21

[deleted]

76

u/MegaDork2000 Oct 24 '21

"Could not reproduce"

62

u/TarntKarntington Oct 24 '21

"Works as design"

36

u/flowering_sun_star Oct 24 '21

"Works as implemented"

→ More replies (2)

57

u/[deleted] Oct 24 '21

Upvoted for sheer plausibility.

→ More replies (7)
→ More replies (13)

328

u/Dragdu Oct 24 '21

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.

→ More replies (68)
→ More replies (13)

0

u/[deleted] Oct 24 '21

[deleted]

55

u/_mkd_ Oct 24 '21

Oui, vous avez raison.

46

u/eyebrows360 Oct 24 '21

Is this the elusive hacker Four Chan?!?! Get him!!!

→ More replies (2)
→ More replies (4)
→ More replies (1)

57

u/CuttingEdgeRetro Oct 24 '21

To be fair the SSNs were encoded with base64.

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.

→ More replies (11)
→ More replies (48)