ID CVE-2011-3085
Summary The Autofill feature in Google Chrome before 19.0.1084.46 does not properly restrict field values, which allows remote attackers to cause a denial of service (UI corruption) and possibly conduct spoofing attacks via vectors involving long values.
References
Vulnerable Configurations
  • Google Chrome 19.0.1084.45
    cpe:2.3:a:google:chrome:19.0.1084.45
CVSS
Base: 5.0 (as of 16-05-2012 - 11:09)
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
NONE NONE PARTIAL
nessus via4
  • NASL family Windows
    NASL id GOOGLE_CHROME_19_0_1084_46.NASL
    description The version of Google Chrome installed on the remote host is earlier than 19.0.1084.46 and is, therefore, affected by the following vulnerabilities : - Video content with FTP can cause crashes. (CVE-2011-3083) - Internal links are not loaded in their own process. (CVE-2011-3084) - Lengthy auto-filled values can corrupt the user interface. (CVE-2011-3085) - Use-after free errors exist related to style elements, table handling, indexed DBs, GTK 'omnibox' handling, and corrupt font encoding names related to PDF handling. (CVE-2011-3086, CVE-2011-3089, CVE-2011-3091, CVE-2011-3096, CVE-2011-3099) - An error exists related to windows navigation. (CVE-2011-3087) - Out-of-bounds read errors exist related to hairline drawing, glyph handling, Tibetan, OGG containers, PDF sampled functions and drawing dash paths. (CVE-2011-3088, CVE-2011-3093, CVE-2011-3094, CVE-2011-3095, CVE-2011-3097, CVE-2011-3100) - A race condition related to workers exists. (CVE-2011-3090) - An invalid write exists in the v8 regex processing. (CVE-2011-3092) - An error exists related to Windows Media Player plugin and the search path. (CVE-2011-3098) - An off-by-one out-of-bounds write error exists in libxml. (CVE-2011-3102)
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 59117
    published 2012-05-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59117
    title Google Chrome < 19.0.1084.46 Multiple Vulnerabilities
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201205-03.NASL
    description The remote host is affected by the vulnerability described in GLSA-201205-03 (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. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-11
    plugin id 59627
    published 2012-06-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59627
    title GLSA-201205-03 : Chromium, V8: Multiple vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2012-295.NASL
    description Chromium update to 21.0.1145 - Fixed several issues around audio not playing with videos - Crash Fixes - Improvements to trackpad on Cr-48 - Security Fixes (bnc#762481) - CVE-2011-3083: Browser crash with video + FTP - CVE-2011-3084: Load links from internal pages in their own process. - CVE-2011-3085: UI corruption with long autofilled values - CVE-2011-3086: Use-after-free with style element. - CVE-2011-3087: Incorrect window navigation - CVE-2011-3088: Out-of-bounds read in hairline drawing - CVE-2011-3089: Use-after-free in table handling. - CVE-2011-3090: Race condition with workers. - CVE-2011-3091: Use-after-free with indexed DB - CVE-2011-3092: Invalid write in v8 regex - CVE-2011-3093: Out-of-bounds read in glyph handling - CVE-2011-3094: Out-of-bounds read in Tibetan handling - CVE-2011-3095: Out-of-bounds write in OGG container. - CVE-2011-3096: Use-after-free in GTK omnibox handling. - CVE-2011-3098: Bad search path for Windows Media Player plug-in - CVE-2011-3100: Out-of-bounds read drawing dash paths. - CVE-2011-3101: Work around Linux Nvidia driver bug - CVE-2011-3102: Off-by-one out-of-bounds write in libxml.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74634
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74634
    title openSUSE Security Update : chromium / v8 (openSUSE-SU-2012:0656-1)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_1449AF379EBA11E1B9C100262D5ED8EE.NASL
    description Google Chrome Releases reports : [112983] Low CVE-2011-3083: Browser crash with video + FTP. Credit to Aki Helin of OUSPG. [113496] Low CVE-2011-3084: Load links from internal pages in their own process. Credit to Brett Wilson of the Chromium development community. [118374] Medium CVE-2011-3085: UI corruption with long autofilled values. Credit to 'psaldorn'. [118642] High CVE-2011-3086: Use-after-free with style element. Credit to Arthur Gerkis. [118664] Low CVE-2011-3087: Incorrect window navigation. Credit to Charlie Reis of the Chromium development community. [120648] Medium CVE-2011-3088: Out-of-bounds read in hairline drawing. Credit to Aki Helin of OUSPG. [120711] High CVE-2011-3089: Use-after-free in table handling. Credit to miaubiz. [121223] Medium CVE-2011-3090: Race condition with workers. Credit to Arthur Gerkis. [121734] High CVE-2011-3091: Use-after-free with indexed DB. Credit to Google Chrome Security Team (Inferno). [122337] High CVE-2011-3092: Invalid write in v8 regex. Credit to Christian Holler. [122585] Medium CVE-2011-3093: Out-of-bounds read in glyph handling. Credit to miaubiz. [122586] Medium CVE-2011-3094: Out-of-bounds read in Tibetan handling. Credit to miaubiz. [123481] High CVE-2011-3095: Out-of-bounds write in OGG container. Credit to Hannu Heikkinen. [Linux only] [123530] Low CVE-2011-3096: Use-after-free in GTK omnibox handling. Credit to Arthur Gerkis. [123733] [124182] High CVE-2011-3097: Out-of-bounds write in sampled functions with PDF. Credit to Kostya Serebryany of Google and Evgeniy Stepanov of Google. [124479] High CVE-2011-3099: Use-after-free in PDF with corrupt font encoding name. Credit to Mateusz Jurczyk of Google Security Team and Gynvael Coldwind of Google Security Team. [124652] Medium CVE-2011-3100: Out-of-bounds read drawing dash paths. Credit to Google Chrome Security Team (Inferno).
    last seen 2019-02-21
    modified 2013-06-21
    plugin id 59103
    published 2012-05-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=59103
    title FreeBSD : chromium -- multiple vulnerabilities (1449af37-9eba-11e1-b9c1-00262d5ed8ee)
oval via4
accepted 2013-08-12T04:07:24.102-04:00
class vulnerability
contributors
  • name Shane Shaffer
    organization G2, Inc.
  • 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 The Autofill feature in Google Chrome before 19.0.1084.46 does not properly restrict field values, which allows remote attackers to cause a denial of service (UI corruption) and possibly conduct spoofing attacks via vectors involving long values.
family windows
id oval:org.mitre.oval:def:15256
status accepted
submitted 2012-05-16T08:35:52.000-04:00
title The Autofill feature in Google Chrome before 19.0.1084.46 does not properly restrict field values
version 44
refmap via4
bid 53540
confirm
gentoo GLSA-201205-03
sectrack 1027067
suse openSUSE-SU-2012:0656
xf google-autofilled-code-execution(75590)
Last major update 29-10-2012 - 23:55
Published 15-05-2012 - 20:55
Last modified 28-12-2017 - 21:29
Back to Top