From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202003-59 ] libvpx: User-assisted execution of arbitrary code
Date: Thu, 26 Mar 2020 19:40:26 +0100 [thread overview]
Message-ID: <88417463-217e-bed6-505b-7a410ceeb273@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3147 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202003-59
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: libvpx: User-assisted execution of arbitrary code
Date: March 26, 2020
Bugs: #701834
ID: 202003-59
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in libvpx, the worst of which
could result in the execution of arbitrary code.
Background
==========
libvpx is the VP8 codec SDK used to encode and decode video streams,
typically within a WebM format media file.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 media-libs/libvpx < 1.8.1 *>= 1.7.0-r1
*>= 1.8.1
Description
===========
Multiple vulnerabilities have been discovered in libvpx. Please review
the CVE identifiers referenced below for details.
Impact
======
A remote attacker could entice a user to open a specially crafted media
file, possibly resulting in the execution of arbitrary code with the
privileges of the user running the application, or a Denial of Service.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All libvpx 1.7.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=media-libs/libvpx-1.7.0-r1"
All libvpx 1.8.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=media-libs/libvpx-1.8.1"
References
==========
[ 1 ] CVE-2019-9232
https://nvd.nist.gov/vuln/detail/CVE-2019-9232
[ 2 ] CVE-2019-9325
https://nvd.nist.gov/vuln/detail/CVE-2019-9325
[ 3 ] CVE-2019-9371
https://nvd.nist.gov/vuln/detail/CVE-2019-9371
[ 4 ] CVE-2019-9433
https://nvd.nist.gov/vuln/detail/CVE-2019-9433
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202003-59
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 2020 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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
reply other threads:[~2020-03-26 18:41 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=88417463-217e-bed6-505b-7a410ceeb273@gentoo.org \
--to=whissi@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