Gentoo Logo

libvorbis: Multiple vulnerabilities

Content:

1.  Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200806-09 / libvorbis
Release Date June 23, 2008
Latest Revision June 23, 2008: 02
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
media-libs/libvorbis < 1.2.1_rc1 >= 1.2.1_rc1 All supported architectures

Related bugreports: #222085

Synopsis

Multiple vulnerabilities in libvorbis might lead to the execution of arbitrary code.

2.  Impact Information

Background

libvorbis is the reference implementation of the Xiph.org Ogg Vorbis audio file format. It is used by many applications for playback of Ogg Vorbis files.

Description

Will Drewry of the Google Security Team reported multiple vulnerabilities in libvorbis:

  • A zero value for "codebook.dim" is not properly handled, leading to a crash, infinite loop or triggering an integer overflow (CVE-2008-1419).
  • An integer overflow in "residue partition value" evaluation might lead to a heap-based buffer overflow (CVE-2008-1420).
  • An integer overflow in a certain "quantvals" and "quantlist" calculation might lead to a heap-based buffer overflow (CVE-2008-1423).

Impact

A remote attacker could exploit these vulnerabilities by enticing a user to open a specially crafted Ogg Vorbis file or network stream with an application using libvorbis. This might lead to the execution of arbitrary code with the privileges of the user playing the file or a Denial of Service by a crash or CPU consumption.

3.  Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All libvorbis users should upgrade to the latest version:

Code Listing 3.1: Resolution

# emerge --sync
# emerge --ask --oneshot --verbose ">=media-libs/libvorbis-1.2.1_rc1"

4.  References



Print

Page updated June 23, 2008

Summary: This is a Gentoo Linux Security Advisory

Security Team
Contact Address

Donate to support our development efforts.

Copyright 2001-2014 Gentoo Foundation, Inc. Questions, Comments? Contact us.