General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] sack panic CVEs
Date: Tue, 18 Jun 2019 14:23:19 -0700	[thread overview]
Message-ID: <CAA93jw7KGhWE52WAcRfQqpUz=rLVT+D-7_xkyzKQ1iFUH8CSww@mail.gmail.com> (raw)

Apparently people are exploiting this in the wild.

https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-001.md

CeroWrt - if anyone is still running it, does have a web server that
might be vulnerable, same for the ssh port. openwrt as well, well...
*Anybody* with an exposed tcp server of just about any sort on freebsd
or linux seems vulnerable to the first bug, which causes a kernel
panic.

Ironically I had been pushing over on ecn-sane to experiment with
lowering the MSS to keep signal strength up in highly congested
scenarios. Apparently,
someone found another use for the idea.

There is an iptables workaround,, documented here:
https://forum.openwrt.org/t/sack-panic-multiple-tcp-based-remote-denial-of-service-vulnerabilities/39028/7

I remember the "ping O death" which cost me christmas in the early
90s. I've been watching the patches to the kernel land and wishing I
was somewhere else.

-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

                 reply	other threads:[~2019-06-18 21:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7KGhWE52WAcRfQqpUz=rLVT+D-7_xkyzKQ1iFUH8CSww@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox