Bypassing airport security via SQL injection

bamboo , 4 hours ago

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

bradorsomething , 3 hours ago

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 , 55 minutes ago

Good ol’ hanlon’s razor.

Darkassassin07 , 4 hours ago (edited 4 hours ago)

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 , 3 hours ago

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

DeltaTangoLima , 43 minutes ago

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