DPDK announcements
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: security@dpdk.org, security-prerelease@dpdk.org,
	dpdk-announce <announce@dpdk.org>,
	Jason Wang <jasowang@redhat.com>
Subject: Re: [dpdk-announce] DPDK security advisory: CVE-2019-14818
Date: Tue, 12 Nov 2019 15:35:51 +0000	[thread overview]
Message-ID: <71cc363c-b363-d6e1-87d6-3bb30a3587ef@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

And thanks to the "Jason Wang" [1] for reporting the vulnerability, all credits
for discovering the issue goes to him.

[1]
Jason Wang <jasowang@redhat.com>

       reply	other threads:[~2019-11-12 15:35 UTC|newest]

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

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=71cc363c-b363-d6e1-87d6-3bb30a3587ef@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=announce@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=jasowang@redhat.com \
    --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
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;
as well as URLs for NNTP newsgroup(s).