<div dir="ltr">Perhaps that was the hope Mark, the forged headers said 99971 99985 therefore in a valid attempt to block the attack the rule was placed. However the rule has triggered what appears to be (a yet unconfirmed) bug condition resulting in the routers crashing.<div>
<br></div><div style>You start an attack, the provider blocks the attack whilst inadvertently crashing themselves, what more could a dos skipt kiddie want than to watch the network fail without them even trying.</div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 10:36 AM, Mark Tees <span dir="ltr"><<a href="mailto:marktees@gmail.com" target="_blank">marktees@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The mentioned on their blog that config walk likely wrong as it was typed out manually. The rule should have been 99971-99985 if it was legitimate.<br>
<br>
But that was never legitimate. Any attack signature that had a packet size larger than what is real shouldn't have made it in. A guess would be that maybe their detection system picked up packets with forged headers.<br>
<div class="HOEnZb"><div class="h5"><br>
On 04/03/2013, at 9:40 AM, Jonathan Thorpe wrote:<br>
<br>
> There appears to be something a little odd about the rule they've installed.<br>
><br>
> + route 173.X.X.X/32-DNS-DROP {<br>
> + match {<br>
> + destination 173.X.X.X/32;<br>
> + port 53;<br>
> + packet-length [ 99971 99985 ];<br>
> + }<br>
> + then discard;<br>
> + }<br>
><br>
> Specifically, they mention "In this case, our attack profiler output the fact that the attack packets were between 99,971 and 99,985 bytes long". Unless there's a typo in the report, the packet-length statement above only includes the two listed.<br>
><br>
> The other thing that looks weird is that IPv4 supports a maximum packet length header of 16-bits (65,535), so how are packet lengths above this possible?<br>
><br>
> Kind Regards,<br>
> Jonathan<br>
><br>
><br>
><br>
> From: <a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a> [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Jeffrey Sims<br>
> Sent: Monday, 4 March 2013 8:55 AM<br>
> To: Don Gould<br>
> Cc: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br>
> Subject: Re: [AusNOG] Cloudflare offline<br>
><br>
> +1 for a great approach by Cloudflare!<br>
><br>
> Agreed, now people know there is a potential bug in JunOS that eegits of the internet might try again (ie: mimik the packet size again to trigger the bug conditions to crash the network).<br>
><br>
> Collaboration is the key!<br>
><br>
> On Mon, Mar 4, 2013 at 8:31 AM, Don Gould <<a href="mailto:don@bowenvale.co.nz">don@bowenvale.co.nz</a>> wrote:<br>
><br>
><br>
> On 4/03/2013 10:21 a.m., Jethro Carr wrote:<br>
> On Mon, 2013-03-04 at 04:37 +1100, Emily Ozols wrote:<br>
> So... Who's getting fired?<br>
><br>
> <bit of snipping...><br>
><br>
> the key difference<br>
> between a competent engineer and an incompetent one is whether they<br>
> followed processes and handled the disaster in a professional manner.<br>
><br>
> I think a key difference is when people just fess up to a mistake so everyone can learn from it! :)<br>
><br>
> Nothing worse than wondering what caused the stuff up and if you could have been part of the cause.<br>
><br>
> Even worse is making a stuff up that you might not have if you'd just known that someone else had done exactly the same thing the week before but didn't share because they were fearful of not being able to feed their kids the next week.<br>
><br>
> +1 for a great approach by Cloudflare!<br>
><br>
> D<br>
><br>
> --<br>
> Don Gould<br>
> 31 Acheson Ave<br>
> Mairehau<br>
> Christchurch, New Zealand<br>
> Ph: <a href="tel:%2B%2064%203%20348%207235" value="+6433487235">+ 64 3 348 7235</a><br>
> Mobile: <a href="tel:%2B%2064%2021%20114%200699" value="+64211140699">+ 64 21 114 0699</a><br>
><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br></div>