public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201904-24 ] Ming: Multiple vulnerabilities
Date: Wed, 24 Apr 2019 19:58:13 -0400	[thread overview]
Message-ID: <20190424235813.GB29627@monkey> (raw)

[-- Attachment #1: Type: text/plain, Size: 3478 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201904-24
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Ming: Multiple vulnerabilities
     Date: April 24, 2019
     Bugs: #624712, #626498, #646770
       ID: 201904-24

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

Multiple vulnerabilities have been found in Ming, the worst of which
could result in a Denial of Service condition.

Background
==========

A library for generating Macromedia Flash files.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  media-libs/ming            < 0.20181112            >= 0.20181112 

Description
===========

Multiple vulnerabilities have been discovered in Ming. Please review
the CVE identifiers referenced below for details.

Impact
======

Please review the referenced CVE identifiers for details.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Ming users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=media-libs/ming-0.20181112"

References
==========

[  1 ] CVE-2017-11728
       https://nvd.nist.gov/vuln/detail/CVE-2017-11728
[  2 ] CVE-2017-11729
       https://nvd.nist.gov/vuln/detail/CVE-2017-11729
[  3 ] CVE-2017-11730
       https://nvd.nist.gov/vuln/detail/CVE-2017-11730
[  4 ] CVE-2017-11731
       https://nvd.nist.gov/vuln/detail/CVE-2017-11731
[  5 ] CVE-2017-11732
       https://nvd.nist.gov/vuln/detail/CVE-2017-11732
[  6 ] CVE-2017-11733
       https://nvd.nist.gov/vuln/detail/CVE-2017-11733
[  7 ] CVE-2017-11734
       https://nvd.nist.gov/vuln/detail/CVE-2017-11734
[  8 ] CVE-2017-9988
       https://nvd.nist.gov/vuln/detail/CVE-2017-9988
[  9 ] CVE-2017-9989
       https://nvd.nist.gov/vuln/detail/CVE-2017-9989
[ 10 ] CVE-2018-5251
       https://nvd.nist.gov/vuln/detail/CVE-2018-5251
[ 11 ] CVE-2018-5294
       https://nvd.nist.gov/vuln/detail/CVE-2018-5294
[ 12 ] CVE-2018-6315
       https://nvd.nist.gov/vuln/detail/CVE-2018-6315
[ 13 ] CVE-2018-6358
       https://nvd.nist.gov/vuln/detail/CVE-2018-6358
[ 14 ] CVE-2018-6359
       https://nvd.nist.gov/vuln/detail/CVE-2018-6359

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201904-24

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2019 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2019-04-25  0:04 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

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

  git send-email \
    --in-reply-to=20190424235813.GB29627@monkey \
    --to=bman@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.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