ID CVE-2013-0923
Summary The USB Apps API in Google Chrome before 26.0.1410.43 allows remote attackers to cause a denial of service (memory corruption) via unspecified vectors.
Vulnerable Configurations
  • Google Chrome 26.0.1410.42
  • Google Chrome 26.0.1410.41
  • Google Chrome 26.0.1410.40
  • Google Chrome 26.0.1410.39
  • Google Chrome 26.0.1410.38
  • Google Chrome 26.0.1410.37
  • Google Chrome 26.0.1410.36
  • Google Chrome 26.0.1410.35
  • Google Chrome 26.0.1410.34
  • Google Chrome 26.0.1410.33
  • Google Chrome 26.0.1410.32
  • Google Chrome 26.0.1410.31
  • Google Chrome 26.0.1410.30
  • Google Chrome 26.0.1410.29
  • Google Chrome 26.0.1410.28
  • Google Chrome 26.0.1410.27
  • Google Chrome 26.0.1410.26
  • Google Chrome 26.0.1410.25
  • Google Chrome 26.0.1410.24
  • Google Chrome 26.0.1410.23
  • Google Chrome 26.0.1410.22
  • Google Chrome 26.0.1410.21
  • Google Chrome 26.0.1410.20
  • Google Chrome 26.0.1410.19
  • Google Chrome 26.0.1410.18
  • Google Chrome 26.0.1410.17
  • Google Chrome 26.0.1410.16
  • Google Chrome 26.0.1410.15
  • Google Chrome 26.0.1410.14
  • Google Chrome 26.0.1410.12
  • Google Chrome 26.0.1410.11
  • Google Chrome 26.0.1410.10
  • Google Chrome 26.0.1410.9
  • Google Chrome 26.0.1410.8
  • Google Chrome 26.0.1410.7
  • Google Chrome 26.0.1410.6
  • Google Chrome 26.0.1410.5
  • Google Chrome 26.0.1410.4
  • Google Chrome 26.0.1410.3
  • Google Chrome 26.0.1410.2
  • Google Chrome 26.0.1410.1
  • Google Chrome 26.0.1410.0
Base: 5.0 (as of 16-11-2016 - 12:39)
  • 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.
nessus via4
  • NASL family Windows
    NASL id GOOGLE_CHROME_26_0_1410_43.NASL
    description The version of Google Chrome installed on the remote host is a version prior to 26.0.1410.43 and is, therefore, affected by the following vulnerabilities : - Use-after-free errors exist related to 'Web Audio' and the extension bookmarks API. (CVE-2013-0916, CVE-2013-0920) - An out-of-bounds read error exists related to the URL loader. (CVE-2013-0917) - An unspecified error exists related to 'drag and drop' actions and the developer tools. (CVE-2013-0918) - An unspecified error exists related to website process isolation. (CVE-2013-0921) - An error exists related to HTTP basic authentication and brute-force attacks. (CVE-2013-0922) - A memory safety issue exists related to the 'USB Apps' API. (CVE-2013-0923) - A permissions error exists related to extensions API and file permissions. (CVE-2013-0924) - URLs can be leaked to extensions even if the extension does not have the 'tabs' permission. (CVE-2013-0925) - An error exists related to 'active tags' and the paste action that has unspecified impact. (CVE-2013-0926)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 65691
    published 2013-03-26
    reporter Tenable
    title Google Chrome < 26.0.1410.43 Multiple Vulnerabilities
  • 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
    title GLSA-201309-16 : Chromium, V8: Multiple vulnerabilities
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_BDD48858965611E2A9A800262D5ED8EE.NASL
    description Google Chrome Releases reports : [172342] High CVE-2013-0916: Use-after-free in Web Audio. Credit to Atte Kettunen of OUSPG. [180909] Low CVE-2013-0917: Out-of-bounds read in URL loader. Credit to Google Chrome Security Team (Cris Neckar). [180555] Low CVE-2013-0918: Do not navigate dev tools upon drag and drop. Credit to Vsevolod Vlasov of the Chromium development community. [Linux only] [178760] Medium CVE-2013-0919: Use-after-free with pop-up windows in extensions. Credit to Google Chrome Security Team (Mustafa Emre Acer). [177410] Medium CVE-2013-0920: Use-after-free in extension bookmarks API. Credit to Google Chrome Security Team (Mustafa Emre Acer). [174943] High CVE-2013-0921: Ensure isolated web sites run in their own processes. [174129] Low CVE-2013-0922: Avoid HTTP basic auth brute-force attempts. Credit to 't3553r'. [169981] [169972] [169765] Medium CVE-2013-0923: Memory safety issues in the USB Apps API. Credit to Google Chrome Security Team (Mustafa Emre Acer). [169632] Low CVE-2013-0924: Check an extension's permissions API usage again file permissions. Credit to Benjamin Kalman of the Chromium development community. [168442] Low CVE-2013-0925: Avoid leaking URLs to extensions without the tabs permissions. Credit to Michael Vrable of Google. [112325] Medium CVE-2013-0926: Avoid pasting active tags in certain situations. Credit to Subho Halder, Aditya Gupta, and Dev Kar of xys3c (
    last seen 2019-02-21
    modified 2013-12-05
    plugin id 65850
    published 2013-04-08
    reporter Tenable
    title FreeBSD : chromium -- multiple vulnerabilities (bdd48858-9656-11e2-a9a8-00262d5ed8ee)
oval via4
accepted 2013-08-12T04:08:42.850-04:00
class vulnerability
  • name Shane Shaffer
    organization G2, Inc.
  • name Jonathan Baker
    organization The MITRE Corporation
  • name Maria Kedovskaya
    organization ALTX-SOFT
comment Google Chrome is installed
oval oval:org.mitre.oval:def:11914
description The USB Apps API in Google Chrome before 26.0.1410.43 allows remote attackers to cause a denial of service (memory corruption) via unspecified vectors.
family windows
id oval:org.mitre.oval:def:16671
status accepted
submitted 2013-04-08T11:33:10.582-04:00
title The USB Apps API in Google Chrome before 26.0.1410.43 allows remote attackers to cause a denial of service (memory corruption) via unspecified vectors
version 43
refmap via4
Last major update 16-11-2016 - 14:00
Published 28-03-2013 - 08:18
Last modified 18-09-2017 - 21:35
Back to Top