Avelo assists ICE daily with deporting people from the United States:<p><a href="https://bsky.app/profile/jjindc.bsky.social/search?q=avelo" rel="nofollow">https://bsky.app/profile/jjindc.bsky.social/search?q=avelo</a>
The 6 hour claim is interesting, but I highly doubt Avelo (or any airline) would handle 100k requests/sec<p>If we consider that the real major's move about 400k-500k passengers/day, let's be really optimistic and say that they check their booking 6 times a day for the week before they fly. That's around 250 requests/sec.<p>Anyone know about the consumer facing tech stacks at airlines these days? Seems unlikely that they'd have databases that would auto scale 400x...
I doubt their API would handle 100k requests per second. That math was roughly indictive of what the cost to send 100k requests per second would look like. He did mention that that was assuming the target didn't have rate limiting, either intentional or just pure limits of the hardware.
Cloud API gateway providers advertise ~10,000 rps.<p>I think more likely the API would be behind some kind of bot protection that would shut this down before any kind of technical rate limit is reached.
><i>The Avelo team was responsive, professional, and took the findings seriously throughout the disclosure process. They acknowledged the severity, worked quickly to remediate the issues, and maintained clear communication. This is a model example of how organizations should handle security disclosures.</i><p>Sounds like no bug bounty?<p>It's great if OP is happy with the outcome, but it's so infuriating that companies are allowed to leak everyone's data with zero accountability and rely on the kindness of security researchers to do free work to notify them.<p>I wish there was a law that assigned a dollar value to different types of PII leaks and fined the organization that amount with some percentage going to the whistleblower. So a security researcher could approach a vendor and say, "Hi! I discovered vulnerabilities in your system that would result in a $500k fine for you. For $400k, I'll disclose it to you privately, or you can turn me down and I'll receive $250k from your fines."
> I wish there was a law that assigned a dollar value to different types of PII leaks<p>There is. It is called GDPR.<p>Plenty of companies have been fined for leaks like this.<p>Some countries also have whistleblower bounties but, as you might expect, there are some perverse incentives there.
Yeah, as an American, I'm jealous of many aspects of GDPR. I really appreciate you blogging / tooting about experiences protecting your rights under GDPR. I wish we had 1/10th of the consumer privacy protections you have.<p>How does security research like this work out in practice, in the EU?<p>I read a lot of vulnerability writeups like this and don't recall seeing any where the author is European and gets a better outcome. Are security researchers actually compensated for this type of work in the EU?
The GDPR (in art 32) only requires that "the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk". I expect it's quite common for a company to get hacked even if they meet that level. I think the parent comment was imagining that any leak is automatically fined, regardless of whether the company had met some security requirement.
Does GDPR mandate a payout to the researcher after disclosure?
The GPDR makes it so small companies need to hire expensive lawyers to be compliant (and you still don't know for sure, based on the laws)<p>How about fining individual developers with poor coding practices?
No it actually doesn't. It just needs someone in the company executive to not have their head up their ass, and read the law, which is fairly straightforward.<p>Also, it needs your company's business model to not be selling user data. That's why American companies find it hard to comply with.
It does not mean this.
> it's so infuriating that companies are allowed to leak everyone's data with zero accountability and rely on the kindness of security researchers to do free work to notify them.<p>This is a matter for lawmakers and law enforcement. Campaign for it. Nothing will change otherwise
Always consider rate limiting if you deploy a public endpoint. Always require authentication to perform resource-consuming and/or privacy leaking requests.
(Requiring authentication makes rate limiting more practical since even a distributed attacker would need many credentials, which they probably don't have).
The lack of needing the last name might have allowed a hacker to brute force the whole list; but it seems that even with a last name, it could expose a lot of PII. Just pass codes along with popular last names (Smith, Jones, Nelson, etc.) and it seems like it could spit out a bunch of reservations.
I'd go for wang, Li and Zhang instead, maybe also Patel and Nguyen. Asian countries have a much more skewed surname distribution.
Yes, it's also an issue when someone posts their bag tag/boarding pass/booking email online.<p>But that's the "industry standard" for checking a reservation online. Requiring airline login doesn't work because of tickets issued by travel agents or other airlines.
Exactly, I came here to say this!<p>> This two-factor system is generally secure. The space of all 6-character alphanumeric confirmation codes combined with all possible last names is astronomically large, making it impossible to “guess” a valid pair.<p>Depending on the threat model, the attacker's goal might not be to guess a single pair but to access <i>any</i> valid pair (of a booking with a flight date in the future, or maybe even in the past). Suddenly you're looking at <i>thousands</i> of valid booking codes and the attacker can try a couple dozen of common names. Brute-forcing valid pairs then becomes relatively easy.
> They were responsive, professional, and took the findings seriously, patching the issues promptly.<p>The "issue" is that they're returning the entire PNR dataset to the front-end in the first place. He doesn't detail how they fixed it, but there's no reason in the world that this entire dataset should be dumped into Javascript. I got into pretty heated arguments with folks about this at Travelocity and this shit is exactly why I was so adamant.
Do we know what GDS Avelo is using? In other GDSes, is the confirmation code always sufficient to fully identify a booking? I was under the impression that PRLs could be re-used as long as the passenger surname was different.<p>The space of all possible PRLs is about 2 billion, I can imagine a really big Airline moving that many passengers.
They use a service of Sabre but not Sabre GDS. it’s called Radixx.<p>Yes in other GDS, it can be enough to identify a full booking. That’s why airlines prefer ticket or coupon number since the first two digits are the airline ticket stock / identifier and then fare codes, etc<p>The requiring last name, and more info is more or less security since any pss system can query the airline first for that combination before requiring more info to return a match.
Confirmation codes are not sufficient on their own, they cycle through them relatively quickly so they have to be combined with things like the passengers family name to actually identify the booking.
Great work, very impressive find.
> I immediately disclosed this to the Avelo team. They were responsive, <i>professional</i>, and took the findings seriously, patching the issues <i>promptly</i>.<p>(emphasis my own)<p>Sorry but I strongly disagree with this phrasing. This is a company "serving over 6 million customers since its 2021 launch" (from Google) that took <i>four weeks</i> to patch an embarrassing security flaw, after being handed all the details on a silver platter.<p>Imagine a food chain serving a million meals a year was revealed to be storing their food products in unsanitary conditions, and it took them <i>a full month</i> to correct this. That story would make national headlines, not to mention they could get promptly shut down by any competent health ministry.<p>I think this attitude mostly reveals how complacent we've become about these """incidents""": we just expect this to happen, everywhere and all the time, then we just shrug and say "they fixed it within a month, how responsible of them".
Annoying sensationalist writing, but good find!
Major? Avelo?
Agreed. I read the headline as "... US Airlines' ..." not "... US Airline's ..." and it seemed much more concerning. Instead it's a single airline I've never heard of. Looking them up, they are more established than I might have guessed (started as Casino Express Airlines 38 years ago, but current incarnation is only 4 years old), but also pretty small - roughly 1/100 the staff and 1/50 the fleet of United.<p><a href="https://en.wikipedia.org/wiki/Avelo_Airlines" rel="nofollow">https://en.wikipedia.org/wiki/Avelo_Airlines</a>
This is about a non-rate-limited endpoint providing ticket data given a booking code <i>only</i> (and not last name as it's usually the case), which makes it feasible to bruteforce the entire search space.<p>(unfortunately, I feel like AI was overused in authoring the writeup)
Is it really AI slop if someone leverages AI to improve / transform their novel experiences and ideas into a rendition that they prefer?<p>I'm not suggesting whether or not the article is AI assisted. I'm wondering if the ease of calling someone's work "AI slop" is a step along the slippery slope towards trivializing this sort of drive-by hostility that can be toxic in a community.
You are right about the toxicity, I will edit my comment.<p>There's a difference between leveraging AI to proofread or improve parts of their writing and this - I feel like AI was <i>overused</i> here; gave the whole article that distinctive smell and significantly reduced its information density.
What makes you say that? This didn't read like AI slop to me.
Overuse of bulleted lists, unnecessary sensationalism, sentences like "The requests flew. There was no WAF, no IP blocking, no CAPTCHA." and so on. It reeks of someone pasting some notes into a chat prompt and asking it to spruce it up for publication.
Pattern recognition skill issue then. It did to me.<p>"The fallout"<p>This flaw was critical.<p>And other vibes. You know it when you see it, though it may be hard to define.
> You know it when you see it<p>How do you know your perception is accurate? One of humanity's biggest weaknesses is trusting that kind of response.
Maybe just try having confidence in yourself. Trust your instincts. I'm not going to impugn my own abilities based on some purported flaw in an abstract amorphous blog called "humanity", whatever that is. A lot of individuals of distinction have many characteristics better than the average, why wouldn't I trust myself more than other people?<p>Pattern recognition is a many millions of years evolved ability best exemplified in the "human" species by the way, so I basically disagree with your whole premise anyways.
The Brown killer was basically caught by a homeless man getting a bad vehicle about the future shooter. So I agree, trusting your gut is definitely a thing.
People believe in witchcraft and lots of other things - including many horrible prejudices - just as confidently as you. There's a reason any scholarship, courts, medicine, and any other serious endeavors require objective evidence.<p>Imagine that - doctors, who have seen everything, have years of study, treat all those people, still require objective evidence. Anyone in IT looks for objective evidence - timing, stepping through code, etc.<p>Confidence doesn't correlate well with accuracy; in fact the more someone expresses your kind of confidence, the less I rely on them at all.<p>What if you wrongfully accuse someone? Does that matter? Are you responsible for the consequences of what you do?
You turn your brain off and outsource your thinking to other people, because you're incapable of perceiving reality for yourself, is what you're telling me.<p>Of course everyone is responsible for their accuracy and their errors, doesn't mean it's impossible to infer things based on observation experience and intuition. This is an evolved ability, but I do agree some people are better than others like most things.<p>You're conflating a lot of things. Many prejudices are accurate and prudent, which craft is stupid, but so what? I'm not going to deny my perception on something that's correct just because some other idiot believes in magic; non sequitur.
It's really a bizarre argument. You are making evidence-free claims, based on nothing - including the things you say about me. It discards all of critical thought, empiricism, reasoning, philosophy, etc. ....
It's definitely AI dude
What is the AI slop version of “This looks shopped. I can tell from some of the pixels and from seeing quite a few shops in my time.”<p>?
> This incident is a stark reminder<p>A stark reminder is a stark reminder about the existence of AI slop. You see the phrase a lot in social media comment spam.
There's an emdash, no human being uses emdashes.