News for hackers. Stuff that matters.
Re:AWS's Egregious Egress by linuxftw on Friday July 23, 2021 @11:09AM (#27931529)
If there's an IP exposed on the internet, you can just send it tcp payloads. The end destination will silently drop them, but it doesn't mean people can't send you gigs of useless data.
Re:AWS's Egregious Egress by otterley on Friday July 23, 2021 @12:53PM (#27932845)
I think you mean UDP. TCP requires a 3-way handshake first.
Re:AWS's Egregious Egress by ithkuil on Friday July 23, 2021 @01:09PM (#27933067)
Intermediate routers don't care about that; they only forward the IP packets; four target host/firewall will drop them (because they don't belong to a valid connection) but they will be still accounted for as ingress traffic.
Re:AWS's Egregious Egress by otterley on Friday July 23, 2021 @09:15PM (#27937563)
Correct, but you can't get much bandwidth through until the 3-way handshake is completed. Sending a bunch of unanswered SYN packets isn't really a great way to instigate a DDoS, compared to sending avalanches of 64KiB UDP packets.
Re:AWS's Egregious Egress by ithkuil on Saturday July 24, 2021 @06:13AM (#27939640)
As long as there is no connection tracking you can send whatever crap you want, including replayed packets from the middle of a connection, perhaps even huge packets with a syn flag ... As long as the accounting happens before a firewall performs basic TCP sanity checks you're going to pay for it
Re:AWS's Egregious Egress by kazen44 on Saturday July 24, 2021 @09:38AM (#27940833)
in some setups, you could send non IP packets (especially in MPLS fabric if accounting happens by LSP).