Cybersecurity

5745 readers

393 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

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

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

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.

you are viewing a single comment's thread
view the rest of the comments

[–] jonne@infosec.pub 4 points 2 months ago (1 children)

Just amazing.

[–] ravhall@discuss.online 2 points 2 months ago (2 children)

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) (1 children)

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 (1 children)

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 (1 children)

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 (1 children)

😭 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.