DPDK announcements
 help / color / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-announce <announce@dpdk.org>
Cc: dpdk-dev <dev@dpdk.org>, security@dpdk.org, security-prerelease@dpdk.org
Subject: Re: [dpdk-announce] [dpdk-security] DPDK security advisory: CVE-2019-14818
Date: Thu, 14 Nov 2019 11:25:04 +0000
Message-ID: <69c30782-8079-1c92-624d-32c19110dc84@intel.com> (raw)
In-Reply-To: <b45c3416-0b1d-0ee4-89eb-c23a69e7cef3@intel.com>

On 11/12/2019 3:15 PM, Ferruh Yigit wrote:
> A vulnerability was fixed in DPDK.
> 
> Some downstream stakeholders were warned in advance in order to coordinate the
> release of fixes and reduce the vulnerability window.
> 
> Problem:
> A malicious container which has direct access to the vhost-user socket can keep
> sending messages which may cause leaking resources until resulting a DOS.
> 
> All users of the vhost library are strongly encouraged to upgrade as soon as
> possible.
> 
> CVE-2019-14818
> Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=363
> Severity: Medium
> CVSS scores: 6.8
> 
> 
> 
> Commits:
> main repo
> https://git.dpdk.org/dpdk/commit/?id=612e17cf6d7b
> https://git.dpdk.org/dpdk/commit/?id=bf472259dde6
> 
> 19.08.1
> https://git.dpdk.org/dpdk-stable/commit/?h=19.08&id=fa674d08985f
> https://git.dpdk.org/dpdk-stable/commit/?h=19.08&id=6547dd563ea9
> 
> 18.11.4 (LTS)
> https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=70583a6b9b1c
> https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=f8898927bb16
> 
> 17.11.8 (LTS)
> https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=3b1b44a1c82a
> https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=8a8dbd0ec19e
> https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=1f6147d9a01f
> 
> 16.11.10 (LTS EOL)
> https://git.dpdk.org/dpdk-stable/commit/?h=16.11&id=5fbb5c2919b6
> https://git.dpdk.org/dpdk-stable/commit/?h=16.11&id=3863340f93b8
> https://git.dpdk.org/dpdk-stable/commit/?h=16.11&id=8790f4c3bcd2
> https://git.dpdk.org/dpdk-stable/commit/?h=16.11&id=1bf11cfb7c7c
> 

A regression has been found on the above commits when VHOST_USER_VRING_NOFD_MASK
is set, there is a suggested fix [1], review and testing is going on.
We are planning to have an update tomorrow.

Sorry for the inconvenience caused.

[1]
https://patches.dpdk.org/patch/62956/

  parent reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b45c3416-0b1d-0ee4-89eb-c23a69e7cef3@intel.com>
2019-11-12 15:35 ` [dpdk-announce] " Ferruh Yigit
2019-11-14 11:25 ` Ferruh Yigit [this message]
2019-11-15 18:19   ` [dpdk-announce] [dpdk-security] " Ferruh Yigit

Reply instructions:

You may reply publically 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=69c30782-8079-1c92-624d-32c19110dc84@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=announce@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=security-prerelease@dpdk.org \
    --cc=security@dpdk.org \
    /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

DPDK announcements

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/announce/0 announce/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 announce announce/ http://inbox.dpdk.org/announce \
		announce@dpdk.org
	public-inbox-index announce


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.announce


AGPL code for this site: git clone https://public-inbox.org/ public-inbox