this post was submitted on 30 Aug 2024
182 points (98.9% liked)

Technology

35137 readers
41 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
[email protected]
182
Bypassing airport security via SQL injection (ian.sh)
submitted 3 months ago by [email protected] to c/[email protected]
15 comments fedilink hide all child comments
 

cross-posted from: https://fed.dyne.org/post/228188

top 15 comments
sorted by: hot top controversial new old
[–] [email protected] 96 points 3 months ago (3 children)

The TSA press office said in a statement that this vulnerability could not be used to access a KCM checkpoint because the TSA initiates a vetting process before issuing a KCM barcode to a new member. However, a KCM barcode is not required to use KCM checkpoints, as the TSO can enter an airline employee ID manually. After we informed the TSA of this, they deleted the section of their website that mentions manually entering an employee ID, and did not respond to our correction. We have confirmed that the interface used by TSOs still allows manual input of employee IDs.

TSA: lalala i can't hear you, everything is fine, no issue here

[–] [email protected] 32 points 3 months ago* (last edited 3 months ago) (1 children)

If Security through Obscurity isn’t working, consider Security through Stupidity, I guess.

I worked with some oilfield SCADS folks in the early 2000’s who used open IP for their valves, who were very convinced no one would use their equipment because “no one knew they were there.” At some point, it’s no longer trust in good actors.

Compliments to the authors, someone owes these guys challenge coins.

[–] Botzo 3 points 3 months ago

Good ol' hanlon's razor.

[–] jaybone 20 points 3 months ago* (last edited 3 months ago) (1 children)

TSA is such a joke. And now we’ll never be rid of them. Thanks Al Quaida, you have successfully achieved your goal of inconveniencing the infidel travelers for decades now. I hope you are happy with yourselves.

[–] [email protected] 6 points 3 months ago (1 children)

They were created for the purpose of security theater. That intent won't to away with time

[–] TechnologyChef 2 points 3 months ago

It seems also harmful to our humanity of Amendments treating disabled, brown, and black people without suspicion and abuse.

[–] [email protected] 1 points 3 months ago

100% not true.

A bar code is required for KCM. Has been for a while now. Manual entries have not been allowed for quite some time.

[–] [email protected] 63 points 3 months ago* (last edited 3 months ago) (1 children)

WOW.

I can understand making a mistake in the website design, leaving such a vulnerability; but to shove it under the rug and ghost the people that reported it???

The TSA and DHS are begging for an incident.

Glad Ian Carroll+Sam Curry made the info public. Maybe that'll be the push needed to actually fix this.

[–] astanix 35 points 3 months ago (1 children)

I would be shocked if they don't get enhanced screening every time now... or placed on the do not fly list.

[–] [email protected] 13 points 3 months ago

Ahhh, the classic "shoot the messengers" defense.

[–] [email protected] 31 points 3 months ago

Fucking hell. Where's the incentive for responsible disclosure, if that's the sort of (non) response you get?

[–] [email protected] 30 points 3 months ago (1 children)

I'm sorry, but WTF is

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.

They are the company, running the thing. You are going to alarm them a whole lot more by going to the damn DHS. Like, I think DHS and TSA probably do need to know about this, but why not start with the actual intimately responsible party?

[–] [email protected] 7 points 3 months ago

I also didn't understand the logic here. Why did they "did not want to alarm them"? Is it because a one person company can simply fix the issue and not report to any other authority? What is the rationale behind it?

[–] [email protected] 13 points 3 months ago (1 children)

This story is hilarious. TSA is comically incompetent.

[–] TechnologyChef 1 points 3 months ago

It seems also harmful to our humanity of Amendments treating disabled, brown, and black people without suspicion and abuse.