ID CVE-2012-5144
Summary Google Chrome before 23.0.1271.97, and Libav 0.7.x before 0.7.7 and 0.8.x before 0.8.5, do not properly perform AAC decoding, which allows remote attackers to cause a denial of service (stack memory corruption) or possibly have unspecified other impact via vectors related to "an off-by-one overwrite when switching to LTP profile from MAIN."
References
Vulnerable Configurations
  • Canonical Ubuntu Linux 11.10
    cpe:2.3:o:canonical:ubuntu_linux:11.10
  • Canonical Ubuntu Linux 12.04 LTS
    cpe:2.3:o:canonical:ubuntu_linux:12.04:-:-:-:lts
  • Canonical Ubuntu Linux 12.10
    cpe:2.3:o:canonical:ubuntu_linux:12.10
  • libav 0.8
    cpe:2.3:a:libav:libav:0.8
  • libav 0.8 beta2
    cpe:2.3:a:libav:libav:0.8:beta2
  • libav 0.8.1
    cpe:2.3:a:libav:libav:0.8.1
  • libav 0.8.2
    cpe:2.3:a:libav:libav:0.8.2
  • libav 0.8.3
    cpe:2.3:a:libav:libav:0.8.3
  • libav 0.8.4
    cpe:2.3:a:libav:libav:0.8.4
  • Google Chrome 23.0.1271.0
    cpe:2.3:a:google:chrome:23.0.1271.0
  • Google Chrome 23.0.1271.1
    cpe:2.3:a:google:chrome:23.0.1271.1
  • Google Chrome 23.0.1271.2
    cpe:2.3:a:google:chrome:23.0.1271.2
  • Google Chrome 23.0.1271.3
    cpe:2.3:a:google:chrome:23.0.1271.3
  • Google Chrome 23.0.1271.4
    cpe:2.3:a:google:chrome:23.0.1271.4
  • Google Chrome 23.0.1271.5
    cpe:2.3:a:google:chrome:23.0.1271.5
  • Google Chrome 23.0.1271.6
    cpe:2.3:a:google:chrome:23.0.1271.6
  • Google Chrome 23.0.1271.7
    cpe:2.3:a:google:chrome:23.0.1271.7
  • Google Chrome 23.0.1271.8
    cpe:2.3:a:google:chrome:23.0.1271.8
  • Google Chrome 23.0.1271.9
    cpe:2.3:a:google:chrome:23.0.1271.9
  • Google Chrome 23.0.1271.10
    cpe:2.3:a:google:chrome:23.0.1271.10
  • Google Chrome 23.0.1271.11
    cpe:2.3:a:google:chrome:23.0.1271.11
  • Google Chrome 23.0.1271.12
    cpe:2.3:a:google:chrome:23.0.1271.12
  • Google Chrome 23.0.1271.13
    cpe:2.3:a:google:chrome:23.0.1271.13
  • Google Chrome 23.0.1271.14
    cpe:2.3:a:google:chrome:23.0.1271.14
  • Google Chrome 23.0.1271.15
    cpe:2.3:a:google:chrome:23.0.1271.15
  • Google Chrome 23.0.1271.16
    cpe:2.3:a:google:chrome:23.0.1271.16
  • Google Chrome 23.0.1271.17
    cpe:2.3:a:google:chrome:23.0.1271.17
  • Google Chrome 23.0.1271.18
    cpe:2.3:a:google:chrome:23.0.1271.18
  • Google Chrome 23.0.1271.19
    cpe:2.3:a:google:chrome:23.0.1271.19
  • Google Chrome 23.0.1271.20
    cpe:2.3:a:google:chrome:23.0.1271.20
  • Google Chrome 23.0.1271.21
    cpe:2.3:a:google:chrome:23.0.1271.21
  • Google Chrome 23.0.1271.22
    cpe:2.3:a:google:chrome:23.0.1271.22
  • Google Chrome 23.0.1271.23
    cpe:2.3:a:google:chrome:23.0.1271.23
  • Google Chrome 23.0.1271.24
    cpe:2.3:a:google:chrome:23.0.1271.24
  • Google Chrome 23.0.1271.26
    cpe:2.3:a:google:chrome:23.0.1271.26
  • Google Chrome 23.0.1271.30
    cpe:2.3:a:google:chrome:23.0.1271.30
  • Google Chrome 23.0.1271.31
    cpe:2.3:a:google:chrome:23.0.1271.31
  • Google Chrome 23.0.1271.32
    cpe:2.3:a:google:chrome:23.0.1271.32
  • Google Chrome 23.0.1271.33
    cpe:2.3:a:google:chrome:23.0.1271.33
  • Google Chrome 23.0.1271.35
    cpe:2.3:a:google:chrome:23.0.1271.35
  • Google Chrome 23.0.1271.36
    cpe:2.3:a:google:chrome:23.0.1271.36
  • Google Chrome 23.0.1271.37
    cpe:2.3:a:google:chrome:23.0.1271.37
  • Google Chrome 23.0.1271.38
    cpe:2.3:a:google:chrome:23.0.1271.38
  • Google Chrome 23.0.1271.39
    cpe:2.3:a:google:chrome:23.0.1271.39
  • Google Chrome 23.0.1271.40
    cpe:2.3:a:google:chrome:23.0.1271.40
  • Google Chrome 23.0.1271.41
    cpe:2.3:a:google:chrome:23.0.1271.41
  • Google Chrome 23.0.1271.44
    cpe:2.3:a:google:chrome:23.0.1271.44
  • Google Chrome 23.0.1271.45
    cpe:2.3:a:google:chrome:23.0.1271.45
  • Google Chrome 23.0.1271.46
    cpe:2.3:a:google:chrome:23.0.1271.46
  • Google Chrome 23.0.1271.49
    cpe:2.3:a:google:chrome:23.0.1271.49
  • Google Chrome 23.0.1271.50
    cpe:2.3:a:google:chrome:23.0.1271.50
  • Google Chrome 23.0.1271.51
    cpe:2.3:a:google:chrome:23.0.1271.51
  • Google Chrome 23.0.1271.52
    cpe:2.3:a:google:chrome:23.0.1271.52
  • Google Chrome 23.0.1271.53
    cpe:2.3:a:google:chrome:23.0.1271.53
  • Google Chrome 23.0.1271.54
    cpe:2.3:a:google:chrome:23.0.1271.54
  • Google Chrome 23.0.1271.55
    cpe:2.3:a:google:chrome:23.0.1271.55
  • Google Chrome 23.0.1271.56
    cpe:2.3:a:google:chrome:23.0.1271.56
  • Google Chrome 23.0.1271.57
    cpe:2.3:a:google:chrome:23.0.1271.57
  • Google Chrome 23.0.1271.58
    cpe:2.3:a:google:chrome:23.0.1271.58
  • Google Chrome 23.0.1271.59
    cpe:2.3:a:google:chrome:23.0.1271.59
  • Google Chrome 23.0.1271.60
    cpe:2.3:a:google:chrome:23.0.1271.60
  • Google Chrome 23.0.1271.61
    cpe:2.3:a:google:chrome:23.0.1271.61
  • Google Chrome 23.0.1271.62
    cpe:2.3:a:google:chrome:23.0.1271.62
  • Google Chrome 23.0.1271.64
    cpe:2.3:a:google:chrome:23.0.1271.64
  • Google Chrome 23.0.1271.83
    cpe:2.3:a:google:chrome:23.0.1271.83
  • Google Chrome 23.0.1271.84
    cpe:2.3:a:google:chrome:23.0.1271.84
  • Google Chrome 23.0.1271.85
    cpe:2.3:a:google:chrome:23.0.1271.85
  • Google Chrome 23.0.1271.86
    cpe:2.3:a:google:chrome:23.0.1271.86
  • Google Chrome 23.0.1271.87
    cpe:2.3:a:google:chrome:23.0.1271.87
  • Google Chrome 23.0.1271.88
    cpe:2.3:a:google:chrome:23.0.1271.88
  • Google Chrome 23.0.1271.89
    cpe:2.3:a:google:chrome:23.0.1271.89
  • cpe:2.3:a:google:chrome:23.0.1271.91
    cpe:2.3:a:google:chrome:23.0.1271.91
  • cpe:2.3:a:google:chrome:23.0.1271.92
    cpe:2.3:a:google:chrome:23.0.1271.92
  • cpe:2.3:a:google:chrome:23.0.1271.93
    cpe:2.3:a:google:chrome:23.0.1271.93
  • Google Chrome 23.0.1271.94
    cpe:2.3:a:google:chrome:23.0.1271.94
  • Google Chrome 23.0.1271.95
    cpe:2.3:a:google:chrome:23.0.1271.95
  • Google Chrome 23.0.1271.96
    cpe:2.3:a:google:chrome:23.0.1271.96
  • OpenSUSE 12.1
    cpe:2.3:o:opensuse:opensuse:12.1
  • OpenSUSE 12.2
    cpe:2.3:o:opensuse:opensuse:12.2
  • libav 0.7
    cpe:2.3:a:libav:libav:0.7
  • libav 0.7 beta 1
    cpe:2.3:a:libav:libav:0.7:beta1
  • libav 0.7 beta
    cpe:2.3:a:libav:libav:0.7:beta2
  • libav 0.7.1
    cpe:2.3:a:libav:libav:0.7.1
  • libav 0.7.2
    cpe:2.3:a:libav:libav:0.7.2
  • libav 0.7.3
    cpe:2.3:a:libav:libav:0.7.3
  • libav 0.7.4
    cpe:2.3:a:libav:libav:0.7.4
  • libav 0.7.5
    cpe:2.3:a:libav:libav:0.7.5
  • libav 0.7.6
    cpe:2.3:a:libav:libav:0.7.6
CVSS
Base: 10.0 (as of 05-10-2016 - 14:42)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
nessus via4
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_4D087B35099011E3A9F4BCAEC565249C.NASL
    description Bundled version of libav in gstreamer-ffmpeg contains a number of vulnerabilities.
    last seen 2019-02-21
    modified 2018-11-21
    plugin id 69412
    published 2013-08-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69412
    title FreeBSD : gstreamer-ffmpeg -- Multiple vulnerabilities in bundled libav (4d087b35-0990-11e3-a9f4-bcaec565249c)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2012-867.NASL
    description - Update to 25.0.1362 - Security fixes (bnc#794075) : - CVE-2012-5139: Use-after-free with visibility events - CVE-2012-5140: Use-after-free in URL loader - CVE-2012-5141: Limit Chromoting client plug-in instantiation. - CVE-2012-5142: Crash in history navigation. - CVE-2012-5143: Integer overflow in PPAPI image buffers - CVE-2012-5144: Stack corruption in AAC decoding - Fixed garbled header and footer text in print preview. [Issue: 152893] - Fixed extension action badges with long text. [Issue: 160069] - Disable find if constrained window is shown. [Issue: 156969] - Enable fullscreen for apps windows. [Issue: 161246] - Fixed broken profile with system-wide installation and UserDataDir & DiskCacheDir policy. [Issue: 161336] - Fixed stability crashes like 158747, 159437, 149139, 160914, 160401, 161858, 158747, 156878 - Fixed graphical corruption in Dust. [Issue: 155258] - Fixed scrolling issue. [Issue: 163553]
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74848
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74848
    title openSUSE Security Update : chromium (openSUSE-SU-2012:1682-1)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_51F84E28444E11E2830600262D5ED8EE.NASL
    description Google Chrome Releases reports : [158204] High CVE-2012-5139: Use-after-free with visibility events. Credit to Chamal de Silva. [159429] High CVE-2012-5140: Use-after-free in URL loader. Credit to Chamal de Silva. [160456] Medium CVE-2012-5141: Limit Chromoting client plug-in instantiation. Credit to Google Chrome Security Team (Juri Aedla). [160803] Critical CVE-2012-5142: Crash in history navigation. Credit to Michal Zalewski of Google Security Team. [160926] Medium CVE-2012-5143: Integer overflow in PPAPI image buffers. Credit to Google Chrome Security Team (Cris Neckar). [161639] High CVE-2012-5144: Stack corruption in AAC decoding. Credit to pawlkt.
    last seen 2019-02-21
    modified 2016-05-26
    plugin id 63256
    published 2012-12-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63256
    title FreeBSD : chromium -- multiple vulnerabilities (51f84e28-444e-11e2-8306-00262d5ed8ee)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201309-16.NASL
    description The remote host is affected by the vulnerability described in GLSA-201309-16 (Chromium, V8: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Chromium and V8. Please review the CVE identifiers and release notes referenced below for details. Impact : A context-dependent attacker could entice a user to open a specially crafted website or JavaScript program using Chromium or V8, possibly resulting in the execution of arbitrary code with the privileges of the process or a Denial of Service condition. Furthermore, a remote attacker may be able to bypass security restrictions or have other, unspecified, impact. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 70112
    published 2013-09-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70112
    title GLSA-201309-16 : Chromium, V8: Multiple vulnerabilities
  • NASL family Windows
    NASL id GOOGLE_CHROME_23_0_1271_97.NASL
    description The version of Google Chrome installed on the remote host is earlier than 23.0.1271.97 and is, therefore, affected by the following vulnerabilities : - Use-after-free errors exist related to visibility events and the URL loader. (CVE-2012-5139, CVE-2012-5140) - An unspecified error exists related to instantiation of the 'Chromoting' client plugin. (CVE-2012-5141) - An unspecified error exists related to history navigation that can lead to application crashes. (CVE-2012-5142) - An integer overflow error exists related to the 'PPAPI' image buffers. (CVE-2012-5143) - A stack corruption error exists related to 'AAC' decoding. (CVE-2012-5144) - The bundled version of Adobe Flash Player contains flaws that can lead to arbitrary code execution. (CVE-2012-5676, CVE-2012-5677, CVE-2012-5678) Successful exploitation of some of these issues could lead to an application crash or even allow arbitrary code execution, subject to the user's privileges.
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 63232
    published 2012-12-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=63232
    title Google Chrome < 23.0.1271.97 Multiple Vulnerabilities
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201406-28.NASL
    description The remote host is affected by the vulnerability described in GLSA-201406-28 (Libav: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Libav. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could entice a user to open a specially crafted media file in an application linked against Libav, possibly resulting in execution of arbitrary code with the privileges of the application or a Denial of Service condition. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 76272
    published 2014-06-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=76272
    title GLSA-201406-28 : Libav: Multiple vulnerabilities
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-1705-1.NASL
    description It was discovered that Libav incorrectly handled certain malformed media files. If a user were tricked into opening a crafted media file, an attacker could cause a denial of service via application crash, or possibly execute arbitrary code with the privileges of the user invoking the program. Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 64283
    published 2013-01-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=64283
    title Ubuntu 11.10 / 12.04 LTS / 12.10 : libav vulnerabilities (USN-1705-1)
oval via4
accepted 2013-08-12T04:08:12.776-04:00
class vulnerability
contributors
  • name Shane Shaffer
    organization G2, Inc.
  • name Maria Kedovskaya
    organization ALTX-SOFT
definition_extensions
comment Google Chrome is installed
oval oval:org.mitre.oval:def:11914
description Google Chrome before 23.0.1271.97, and Libav 0.7.x before 0.7.7 and 0.8.x before 0.8.5, do not properly perform AAC decoding, which allows remote attackers to cause a denial of service (stack memory corruption) or possibly have unspecified other impact via vectors related to "an off-by-one overwrite when switching to LTP profile from MAIN."
family windows
id oval:org.mitre.oval:def:16007
status accepted
submitted 2012-12-12T09:25:55.661-05:00
title Google Chrome before 23.0.1271.97 does not properly perform AAC decoding
version 43
refmap via4
confirm
suse openSUSE-SU-2012:1682
ubuntu USN-1705-1
Last major update 06-10-2016 - 12:17
Published 12-12-2012 - 06:38
Last modified 30-10-2018 - 12:27
Back to Top