Vulnerabilities > CVE-2010-3118 - Information Exposure vulnerability in Google Chrome
Attack vector
NETWORK Attack complexity
LOW Privileges required
NONE Confidentiality impact
PARTIAL Integrity impact
NONE Availability impact
NONE Summary
The autosuggest feature in the Omnibox implementation in Google Chrome before 5.0.375.127 does not anticipate entry of passwords, which might allow remote attackers to obtain sensitive information by reading the network traffic generated by this feature.
Vulnerable Configurations
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (CAPEC)
- Subverting Environment Variable Values The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
- Footprinting An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
- Exploiting Trust in Client (aka Make the Client Invisible) An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
- Browser Fingerprinting An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
- Session Credential Falsification through Prediction This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
Nessus
| NASL family | Windows |
| NASL id | GOOGLE_CHROME_5_0_375_127.NASL |
| description | The version of Google Chrome installed on the remote host is earlier than 5.0.375.127. Such versions are reportedly affected by multiple vulnerabilities : - A memory corruption vulnerability exists with the file dialog. (Issue #45400) - A memory corruption vulnerability exists when processing SVG files. (Issue #49596) - A vulnerability exists due to a bad cast with text editing. (Issue #49628) - A vulnerability exists that possibly allows address bar spoofing via a history bug. (Issue #49964) - A memory corruption vulnerability exists in MIME type handling. (Issue #50515, #51835) - A vulnerability exists due to a crash on shutdown via a notifications bug. (Issue #50553) - A vulnerability can be triggered in omnibox autosuggest if the user may be going to type a password. (Issue #51146) - A memory corruption vulnerability exists in ruby support. (Issue #51654) - A memory corruption vulnerability exists in Geolocation support. (Issue #51670) |
| last seen | 2020-06-01 |
| modified | 2020-06-02 |
| plugin id | 48383 |
| published | 2010-08-20 |
| reporter | This script is Copyright (C) 2010-2018 Tenable Network Security, Inc. |
| source | https://www.tenable.com/plugins/nessus/48383 |
| title | Google Chrome < 5.0.375.127 Multiple Vulnerabilities |
| code | |
Oval
| accepted | 2013-08-12T04:00:28.585-04:00 | ||||||||||||||||||||||||
| class | vulnerability | ||||||||||||||||||||||||
| contributors |
| ||||||||||||||||||||||||
| definition_extensions |
| ||||||||||||||||||||||||
| description | The autosuggest feature in the Omnibox implementation in Google Chrome before 5.0.375.127 does not anticipate entry of passwords, which might allow remote attackers to obtain sensitive information by reading the network traffic generated by this feature. | ||||||||||||||||||||||||
| family | windows | ||||||||||||||||||||||||
| id | oval:org.mitre.oval:def:11839 | ||||||||||||||||||||||||
| status | accepted | ||||||||||||||||||||||||
| submitted | 2010-08-25T11:10:59 | ||||||||||||||||||||||||
| title | Vulnerability in autosuggest feature in the Omnibox implementation in Google Chrome before 5.0.375.127 | ||||||||||||||||||||||||
| version | 50 |