From: Daniel Borkmann <dborkman@redhat.com>
To: Joshua Kinard <kumba@gentoo.org>
Cc: davem@davemloft.net, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>
Subject: Re: [PATCH net 1/3] net: sctp: fix skb_over_panic when receiving malformed ASCONF chunks
Date: Fri, 10 Oct 2014 22:06:13 +0000 [thread overview]
Message-ID: <54385855.10401@redhat.com> (raw)
In-Reply-To: <5437AF27.2030506@gentoo.org>
On 10/10/2014 12:04 PM, Joshua Kinard wrote:
...
> If I am reading correctly, this crash can only be triggered by actually getting
> through the SCTP handshake, then sending this specially-crafted ASCONF chunk?
> Meaning a blind nmap scan using this tactic against a random netblock wouldn't
> just randomly knock servers offline? This would seem to reduce the attack
> surface a quite bit by requiring the remote endpoint to actually respond.
Sorry, have been on travel almost whole day ... yes, handshake has to be
completed before that. So a scan/probe would need to establish a connection
first and ASCONF would need to be supported.
> Is there a CVE # for this?
CVE-2014-3673
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: Joshua Kinard <kumba@gentoo.org>
Cc: davem@davemloft.net, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>
Subject: Re: [PATCH net 1/3] net: sctp: fix skb_over_panic when receiving malformed ASCONF chunks
Date: Sat, 11 Oct 2014 00:06:13 +0200 [thread overview]
Message-ID: <54385855.10401@redhat.com> (raw)
In-Reply-To: <5437AF27.2030506@gentoo.org>
On 10/10/2014 12:04 PM, Joshua Kinard wrote:
...
> If I am reading correctly, this crash can only be triggered by actually getting
> through the SCTP handshake, then sending this specially-crafted ASCONF chunk?
> Meaning a blind nmap scan using this tactic against a random netblock wouldn't
> just randomly knock servers offline? This would seem to reduce the attack
> surface a quite bit by requiring the remote endpoint to actually respond.
Sorry, have been on travel almost whole day ... yes, handshake has to be
completed before that. So a scan/probe would need to establish a connection
first and ASCONF would need to be supported.
> Is there a CVE # for this?
CVE-2014-3673
next prev parent reply other threads:[~2014-10-10 22:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 20:55 [PATCH net 0/3] SCTP fixes Daniel Borkmann
2014-10-09 20:55 ` Daniel Borkmann
2014-10-09 20:55 ` [PATCH net 1/3] net: sctp: fix skb_over_panic when receiving malformed ASCONF chunks Daniel Borkmann
2014-10-09 20:55 ` Daniel Borkmann
2014-10-10 10:04 ` Joshua Kinard
2014-10-10 10:04 ` Joshua Kinard
2014-10-10 22:06 ` Daniel Borkmann [this message]
2014-10-10 22:06 ` Daniel Borkmann
2014-10-10 14:48 ` Neil Horman
2014-10-10 14:48 ` Neil Horman
2014-10-09 20:55 ` [PATCH net 2/3] net: sctp: fix panic on duplicate " Daniel Borkmann
2014-10-09 20:55 ` Daniel Borkmann
2014-10-10 15:39 ` Neil Horman
2014-10-10 15:39 ` Neil Horman
2014-10-10 22:02 ` Daniel Borkmann
2014-10-10 22:02 ` Daniel Borkmann
2014-10-12 1:42 ` Neil Horman
2014-10-12 1:42 ` Neil Horman
2014-10-12 7:15 ` Vladislav Yasevich
2014-10-12 7:15 ` Vladislav Yasevich
2014-10-12 23:25 ` Daniel Borkmann
2014-10-12 23:25 ` Daniel Borkmann
2014-10-15 2:58 ` Neil Horman
2014-10-15 2:58 ` Neil Horman
2014-10-15 23:13 ` Daniel Borkmann
2014-10-15 23:13 ` Daniel Borkmann
2014-10-15 7:51 ` Vlad Yasevich
2014-10-15 7:51 ` Vlad Yasevich
2014-10-09 20:55 ` [PATCH net 3/3] net: sctp: fix remote memory pressure from excessive queueing Daniel Borkmann
2014-10-09 20:55 ` Daniel Borkmann
2014-10-14 16:46 ` [PATCH net 0/3] SCTP fixes David Miller
2014-10-14 16:46 ` David Miller
2014-10-15 3:06 ` Neil Horman
2014-10-15 3:06 ` Neil Horman
2014-10-15 4:21 ` David Miller
2014-10-15 4:21 ` David Miller
2014-10-15 20:20 ` Neil Horman
2014-10-15 20:20 ` Neil Horman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54385855.10401@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=kumba@gentoo.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vyasevich@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.