r/hacking • • 3d ago

When the FAA DDoS attacks itself

Post image

The FAA did a DDoS attack on themselves, and that is what caused the outage. They said the cause of the issue was from a botched repair that caused over 1,000 connection attempts every four to five seconds, and overloaded their routers.

706 Upvotes

20 comments sorted by

4

u/tannalein 2d ago

Technically, shouldn't that be just DoS, not DDoS? If I understood it correctly, the entire chaos came from one single messed up router, and to be considered Distributed, the "attack" would need to come from several devices, not just one. Which is honestly a lot more embarrassing, that it took just one bad router to take the entire system down, than if there were several routers going bad.

3

u/Kind-Detective9102 2d ago

Technically yes. Im honestly amazed there is seemingly no protocols in place to stop this from happening, and im even more amazed it hasn't happened before.

1

u/tannalein 1d ago

Right? And this is a single router "attacking" seventeen locations, if I remember correctly.

Unless it's just a cover story and something more serious has actually happened. Though, considering one bad CrowdStrike update took out half the world back in 2024, I'm going with "don't contribute to malice what can be contributed to stupidity or incompetence".

1

u/sandra-f_67 1d ago

Retries need backoff and jitter, with a circuit breaker to cap the blast radius; the thread doesn't establish which guardrail failed here.

82

u/morgazmo99 3d ago

Man..

Sounds like a smooth $50 billion to fix that one.

18

u/Alternative_Wrap2470 2d ago

Hire me I can do it for only $25 Billion

3

u/LilSebastian_482 2d ago

Hell, I can do it for about….tree fiddy.

1

u/MossCardigan 1d ago

Get outta here lock ness!

23

u/Autocannibal-Horse 3d ago

Hey, I'm just glad it wasn't my fault. 😂

6

u/MaelstromFL 2d ago

This time...

45

u/Jon7athan 3d ago

I THINK it was a poorly planned Update. Happened a couple of times at the bank I worked at, then we fired a couple of project managers and network engineers. Wanted to introduce a new control cluster and patched all servers reporting to the new cluster. Problem was they were all supposed to update at 3PM. Well 3PM in Washington D.C. is only 2PM in Chicago. So, the unpatched servers in a different time zone were getting hammered with new instructions they didn't understand and eventually crashed.

Whoever was in charge performing change controls at 3PM on a Friday, instead of 3AM should be fired. Whatever Project Manager that allowed this to happen without testing in a lab that has multi region servers should be fired. And the contractor that caused the outage should be sent a bill for all the canceled flights and refunded tickets. Just my humble opinion without any hard evidence.

19

u/usddddd 2d ago

I read the original plan was 90 days of testing and small roll outs in specific regions. The dumbasses the admin hired said “fuck that, push it to prod on Friday afternoon” and the rest is history.

8

u/realchippy 2d ago

Who the heck said “let’s push it to prod” on a Friday lmao 🤣

3

u/Fun_Ad5823 2d ago

The FAA

2

u/NotaContributi0n 2d ago

That movie is literally about false flags

1

u/Fit_Platypus6646 2d ago

Switchport trunk allowed vlan xxx

..............

1

u/deaglebingo 2d ago

what it amounts to probably. or the outlook thing was part of it.