Vulnerabilities > CVE-2010-3729 - Integer Overflow or Wraparound vulnerability in Google Chrome
Attack vector
NETWORK Attack complexity
LOW Privileges required
NONE Confidentiality impact
HIGH Integrity impact
HIGH Availability impact
HIGH Summary
The SPDY protocol implementation in Google Chrome before 6.0.472.62 does not properly manage buffers, which might allow remote attackers to execute arbitrary code via unspecified vectors.
Vulnerable Configurations
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (CAPEC)
- Forced Integer Overflow This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
Nessus
NASL family | Windows |
NASL id | GOOGLE_CHROME_6_0_472_62.NASL |
description | The version of Google Chrome installed on the remote host is earlier than 6.0.472.62. Such versions are reportedly affected by multiple vulnerabilities : - There is a bad cast with malformed SVGs. (Issue #55114) - The buffer is mismanaged in the SPDY protocol. (Issue #55119) - A cross-origin property pollution issue exists. (Issue #55350) |
last seen | 2020-06-01 |
modified | 2020-06-02 |
plugin id | 49285 |
published | 2010-09-20 |
reporter | This script is Copyright (C) 2010-2018 Tenable Network Security, Inc. |
source | https://www.tenable.com/plugins/nessus/49285 |
title | Google Chrome < 6.0.472.62 Multiple Vulnerabilities |
code |
|
Oval
accepted | 2013-08-12T04:10:14.859-04:00 | ||||||||||||||||||||||||
class | vulnerability | ||||||||||||||||||||||||
contributors |
| ||||||||||||||||||||||||
definition_extensions |
| ||||||||||||||||||||||||
description | The SPDY protocol implementation in Google Chrome before 6.0.472.62 does not properly manage buffers, which might allow remote attackers to execute arbitrary code via unspecified vectors. | ||||||||||||||||||||||||
family | windows | ||||||||||||||||||||||||
id | oval:org.mitre.oval:def:7380 | ||||||||||||||||||||||||
status | accepted | ||||||||||||||||||||||||
submitted | 2010-10-07T17:30:00.000-05:00 | ||||||||||||||||||||||||
title | Google Chrome SPDY Protocol Implementation Buffer Management Weakness Arbitrary Code Execution | ||||||||||||||||||||||||
version | 51 |
References
- http://code.google.com/p/chromium/issues/detail?id=55119
- http://code.google.com/p/chromium/issues/detail?id=55119
- http://googlechromereleases.blogspot.com/2010/09/stable-beta-channel-updates_17.html
- http://googlechromereleases.blogspot.com/2010/09/stable-beta-channel-updates_17.html
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7380
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7380