this post was submitted on 11 Feb 2025
1262 points (98.6% liked)

Programmer Humor

20487 readers
783 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 

See the post on BlueSky: https://bsky.app/profile/provisionalidea.bsky.social/post/3lhujtm2qkc2i

According to many comments, the US government DOES use SQL, and Musk is not understanding much what's going on.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 2 days ago* (last edited 2 days ago) (1 children)

They're sequential, so the values above and below yours are valid SSNs of people born in the same hospital around the same time.

This would make it trivially easy to get access to records you shouldn't

[–] [email protected] 7 points 2 days ago (1 children)

Isn't that assuming you have access to doing arbitrary SQL queries on the database? Then you'd by definition have access to records you shouldn't.

[–] [email protected] 3 points 1 day ago* (last edited 1 day ago)

No. You can have control over specific parameters of an SQL query though. Look up insecure direct object reference vulnerabilities.

Consider a website that uses the following URL to access the customer account page, by retrieving information from the back-end database: https://insecure-website.com/customer_account?customer_number=132355 Here, the customer number is used directly as a record index in queries that are performed on the back-end database. If no other controls are in place, an attacker can simply modify the customer_number value, bypassing access controls to view the records of other customers.