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.
…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!
Why not post the primary source? https://ian.sh/tsa
Understandable. I’m more confused why Bruce ripped off the original blog post.
Cool username, btw
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?
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.
Just amazing.
In 2024, I thought this was pretty much impossible. I guess that software is ancient.
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
The beautiful thing about string injection vulnerabilities is that they will never ever stop happening. It’s just too easy to sprintf untrusted input.
