57
SQL Injection Attack on Airport Security (www.schneier.com)
submitted 2 months ago by 0x0@programming.dev to c/cybersecurity@sh.itjust.works
16 comments fedilink hide all child comments

Anyone with basic knowledge of SQL injection could login to this site and add anyone they wanted to KCM and CASS, allowing themselves to both skip security screening and then access the cockpits of commercial airliners.

top 16 comments
sorted by: hot top controversial new old
[-] polaris64@lemmy.sdf.org 17 points 2 months ago

...We did not want to contact FlyCASS first as it appeared to be operated only by one person and we did not want to alarm them. On April 23rd, we were able to disclose the issue to the Department of Homeland Security, who acknowledged the issue and confirmed that they “are taking this very seriously”.

I think the owner of FlyCASS was sufficiently alarmed!

[-] 0x0@lemmy.dbzer0.com 11 points 2 months ago

Why not post the primary source? https://ian.sh/tsa

[-] 0x0@programming.dev 3 points 2 months ago

Posted the source i found it through.

[-] 0x0@lemmy.dbzer0.com 4 points 2 months ago

Understandable. I'm more confused why Bruce ripped off the original blog post.

Cool username, btw

[-] 0x0@programming.dev 1 points 2 months ago

He does that a lot, although he tends to be more verbose on the topic when he does. Then again, there's not much to this story (the details, not the implications).

[-] cron@feddit.org 6 points 2 months ago

We ended up finding several more serious issues but began the disclosure process immediately after finding the first issue.

How many vulnerabilities can there be in such a safety-critical application?

[-] 0x0@programming.dev 8 points 2 months ago* (last edited 2 months ago)

No for-profit will bother with security unless forced to, as it's seen as an expense and shareholders don't like that.

Edit: also:

We had difficulty identifying the right disclosure contact for this issue. We did not want to contact FlyCASS first as it appeared to be operated only by one person and we did not want to alarm them.

Emphasis mine.

[-] cron@feddit.org 6 points 2 months ago

Oh, the old "this is so obscure, nobody will find this out"-excuse

[-] jonne@infosec.pub 4 points 2 months ago

Just amazing.

[-] ravhall@discuss.online 2 points 2 months ago

In 2024, I thought this was pretty much impossible. I guess that software is ancient.

[-] Telorand@reddthat.com 5 points 2 months ago* (last edited 2 months ago)

Bruh, it's 2024, and banks still don't have app-based or hardware-based TOTP.

I get that upgrading can be hard, but when you're safeguarding people's lives or money (and also PII), I don't understand how it's not a legal mandate that you have to meet certain basic security thresholds.

Edit: typo

[-] taladar@sh.itjust.works 1 points 2 months ago

I assume you meant PII?

[-] Telorand@reddthat.com 1 points 2 months ago

Yes. I should really quit commenting before coffee

[-] 0x0@lemmy.dbzer0.com 1 points 2 months ago

The beautiful thing about string injection vulnerabilities is that they will never ever stop happening. It's just too easy to sprintf untrusted input.

[-] ravhall@discuss.online 2 points 2 months ago

😭 prepare your queries!!!!

[-] 0x0@lemmy.dbzer0.com 3 points 2 months ago

You know, the reason this happens is that you can ask your database to execute a string type, but languages usually don't distinguish between a static string and a dynamically constructed string.

Not to proselytize, but this is a place where rust's lifetime annotations can shine. The DB interface should take a &'static str( and a variable number of parameters to insert) so it can be certain that no untrusted user input has already been injected into the query string. Assuming all static data is trusted, the sql injection vulnerabilities just went poof.

Sadly, it looks like rusqlite's execute() takes a non-static str. I wonder why.

this post was submitted on 03 Sep 2024
57 points (100.0% liked)

Cybersecurity

5631 readers
42 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
kid@sh.itjust.works
Lanky_Pomegranate530@midwest.social