ID CVE-2013-0887
Summary The developer-tools process in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, does not properly restrict privileges during interaction with a connected server, which has unspecified impact and attack vectors.
References
Vulnerable Configurations
  • Google Chrome 25.0.1364.93
    cpe:2.3:a:google:chrome:25.0.1364.93
  • Google Chrome 25.0.1364.92
    cpe:2.3:a:google:chrome:25.0.1364.92
  • Google Chrome 25.0.1364.91
    cpe:2.3:a:google:chrome:25.0.1364.91
  • Google Chrome 25.0.1364.90
    cpe:2.3:a:google:chrome:25.0.1364.90
  • Google Chrome 25.0.1364.89
    cpe:2.3:a:google:chrome:25.0.1364.89
  • Google Chrome 25.0.1364.88
    cpe:2.3:a:google:chrome:25.0.1364.88
  • Google Chrome 25.0.1364.87
    cpe:2.3:a:google:chrome:25.0.1364.87
  • Google Chrome 25.0.1364.86
    cpe:2.3:a:google:chrome:25.0.1364.86
  • Google Chrome 25.0.1364.85
    cpe:2.3:a:google:chrome:25.0.1364.85
  • Google Chrome 25.0.1364.84
    cpe:2.3:a:google:chrome:25.0.1364.84
  • Google Chrome 25.0.1364.82
    cpe:2.3:a:google:chrome:25.0.1364.82
  • Google Chrome 25.0.1364.81
    cpe:2.3:a:google:chrome:25.0.1364.81
  • Google Chrome 25.0.1364.80
    cpe:2.3:a:google:chrome:25.0.1364.80
  • Google Chrome 25.0.1364.79
    cpe:2.3:a:google:chrome:25.0.1364.79
  • Google Chrome 25.0.1364.78
    cpe:2.3:a:google:chrome:25.0.1364.78
  • Google Chrome 25.0.1364.77
    cpe:2.3:a:google:chrome:25.0.1364.77
  • Google Chrome 25.0.1364.76
    cpe:2.3:a:google:chrome:25.0.1364.76
  • Google Chrome 25.0.1364.75
    cpe:2.3:a:google:chrome:25.0.1364.75
  • Google Chrome 25.0.1364.74
    cpe:2.3:a:google:chrome:25.0.1364.74
  • Google Chrome 25.0.1364.73
    cpe:2.3:a:google:chrome:25.0.1364.73
  • Google Chrome 25.0.1364.72
    cpe:2.3:a:google:chrome:25.0.1364.72
  • Google Chrome 25.0.1364.70
    cpe:2.3:a:google:chrome:25.0.1364.70
  • Google Chrome 25.0.1364.68
    cpe:2.3:a:google:chrome:25.0.1364.68
  • Google Chrome 25.0.1364.67
    cpe:2.3:a:google:chrome:25.0.1364.67
  • Google Chrome 25.0.1364.66
    cpe:2.3:a:google:chrome:25.0.1364.66
  • Google Chrome 25.0.1364.65
    cpe:2.3:a:google:chrome:25.0.1364.65
  • Google Chrome 25.0.1364.63
    cpe:2.3:a:google:chrome:25.0.1364.63
  • Google Chrome 25.0.1364.62
    cpe:2.3:a:google:chrome:25.0.1364.62
  • Google Chrome 25.0.1364.61
    cpe:2.3:a:google:chrome:25.0.1364.61
  • Google Chrome 25.0.1364.58
    cpe:2.3:a:google:chrome:25.0.1364.58
  • Google Chrome 25.0.1364.57
    cpe:2.3:a:google:chrome:25.0.1364.57
  • Google Chrome 25.0.1364.56
    cpe:2.3:a:google:chrome:25.0.1364.56
  • Google Chrome 25.0.1364.55
    cpe:2.3:a:google:chrome:25.0.1364.55
  • Google Chrome 25.0.1364.54
    cpe:2.3:a:google:chrome:25.0.1364.54
  • Google Chrome 25.0.1364.53
    cpe:2.3:a:google:chrome:25.0.1364.53
  • Google Chrome 25.0.1364.52
    cpe:2.3:a:google:chrome:25.0.1364.52
  • Google Chrome 25.0.1364.51
    cpe:2.3:a:google:chrome:25.0.1364.51
  • Google Chrome 25.0.1364.50
    cpe:2.3:a:google:chrome:25.0.1364.50
  • Google Chrome 25.0.1364.49
    cpe:2.3:a:google:chrome:25.0.1364.49
  • Google Chrome 25.0.1364.48
    cpe:2.3:a:google:chrome:25.0.1364.48
  • Google Chrome 25.0.1364.47
    cpe:2.3:a:google:chrome:25.0.1364.47
  • Google Chrome 25.0.1364.46
    cpe:2.3:a:google:chrome:25.0.1364.46
  • Google Chrome 25.0.1364.45
    cpe:2.3:a:google:chrome:25.0.1364.45
  • Google Chrome 25.0.1364.44
    cpe:2.3:a:google:chrome:25.0.1364.44
  • Google Chrome 25.0.1364.43
    cpe:2.3:a:google:chrome:25.0.1364.43
  • Google Chrome 25.0.1364.42
    cpe:2.3:a:google:chrome:25.0.1364.42
  • Google Chrome 25.0.1364.41
    cpe:2.3:a:google:chrome:25.0.1364.41
  • Google Chrome 25.0.1364.40
    cpe:2.3:a:google:chrome:25.0.1364.40
  • Google Chrome 25.0.1364.39
    cpe:2.3:a:google:chrome:25.0.1364.39
  • Google Chrome 25.0.1364.38
    cpe:2.3:a:google:chrome:25.0.1364.38
  • Google Chrome 25.0.1364.37
    cpe:2.3:a:google:chrome:25.0.1364.37
  • Google Chrome 25.0.1364.36
    cpe:2.3:a:google:chrome:25.0.1364.36
  • Google Chrome 25.0.1364.35
    cpe:2.3:a:google:chrome:25.0.1364.35
  • Google Chrome 25.0.1364.34
    cpe:2.3:a:google:chrome:25.0.1364.34
  • Google Chrome 25.0.1364.33
    cpe:2.3:a:google:chrome:25.0.1364.33
  • Google Chrome 25.0.1364.32
    cpe:2.3:a:google:chrome:25.0.1364.32
  • Google Chrome 25.0.1364.31
    cpe:2.3:a:google:chrome:25.0.1364.31
  • Google Chrome 25.0.1364.30
    cpe:2.3:a:google:chrome:25.0.1364.30
  • Google Chrome 25.0.1364.29
    cpe:2.3:a:google:chrome:25.0.1364.29
  • Google Chrome 25.0.1364.28
    cpe:2.3:a:google:chrome:25.0.1364.28
  • Google Chrome 25.0.1364.27
    cpe:2.3:a:google:chrome:25.0.1364.27
  • Google Chrome 25.0.1364.26
    cpe:2.3:a:google:chrome:25.0.1364.26
  • Google Chrome 25.0.1364.25
    cpe:2.3:a:google:chrome:25.0.1364.25
  • Google Chrome 25.0.1364.24
    cpe:2.3:a:google:chrome:25.0.1364.24
  • Google Chrome 25.0.1364.23
    cpe:2.3:a:google:chrome:25.0.1364.23
  • Google Chrome 25.0.1364.22
    cpe:2.3:a:google:chrome:25.0.1364.22
  • Google Chrome 25.0.1364.21
    cpe:2.3:a:google:chrome:25.0.1364.21
  • Google Chrome 25.0.1364.20
    cpe:2.3:a:google:chrome:25.0.1364.20
  • Google Chrome 25.0.1364.19
    cpe:2.3:a:google:chrome:25.0.1364.19
  • Google Chrome 25.0.1364.18
    cpe:2.3:a:google:chrome:25.0.1364.18
  • Google Chrome 25.0.1364.17
    cpe:2.3:a:google:chrome:25.0.1364.17
  • Google Chrome 25.0.1364.16
    cpe:2.3:a:google:chrome:25.0.1364.16
  • Google Chrome 25.0.1364.15
    cpe:2.3:a:google:chrome:25.0.1364.15
  • Google Chrome 25.0.1364.14
    cpe:2.3:a:google:chrome:25.0.1364.14
  • Google Chrome 25.0.1364.13
    cpe:2.3:a:google:chrome:25.0.1364.13
  • Google Chrome 25.0.1364.12
    cpe:2.3:a:google:chrome:25.0.1364.12
  • Google Chrome 25.0.1364.11
    cpe:2.3:a:google:chrome:25.0.1364.11
  • Google Chrome 25.0.1364.10
    cpe:2.3:a:google:chrome:25.0.1364.10
  • Google Chrome 25.0.1364.9
    cpe:2.3:a:google:chrome:25.0.1364.9
  • Google Chrome 25.0.1364.8
    cpe:2.3:a:google:chrome:25.0.1364.8
  • Google Chrome 25.0.1364.7
    cpe:2.3:a:google:chrome:25.0.1364.7
  • Google Chrome 25.0.1364.5
    cpe:2.3:a:google:chrome:25.0.1364.5
  • Google Chrome 25.0.1364.3
    cpe:2.3:a:google:chrome:25.0.1364.3
  • Google Chrome 25.0.1364.2
    cpe:2.3:a:google:chrome:25.0.1364.2
  • Google Chrome 25.0.1364.1
    cpe:2.3:a:google:chrome:25.0.1364.1
  • Google Chrome 25.0.1364.0
    cpe:2.3:a:google:chrome:25.0.1364.0
  • Google Chrome 25.0.1364.95
    cpe:2.3:a:google:chrome:25.0.1364.95
  • Microsoft Windows
    cpe:2.3:o:microsoft:windows
  • Linux Kernel
    cpe:2.3:o:linux:linux_kernel
  • Google Chrome 25.0.1364.35
    cpe:2.3:a:google:chrome:25.0.1364.35
  • Google Chrome 25.0.1364.36
    cpe:2.3:a:google:chrome:25.0.1364.36
  • Google Chrome 25.0.1364.33
    cpe:2.3:a:google:chrome:25.0.1364.33
  • Google Chrome 25.0.1364.34
    cpe:2.3:a:google:chrome:25.0.1364.34
  • Google Chrome 25.0.1364.39
    cpe:2.3:a:google:chrome:25.0.1364.39
  • Google Chrome 25.0.1364.40
    cpe:2.3:a:google:chrome:25.0.1364.40
  • Google Chrome 25.0.1364.37
    cpe:2.3:a:google:chrome:25.0.1364.37
  • Google Chrome 25.0.1364.38
    cpe:2.3:a:google:chrome:25.0.1364.38
  • Google Chrome 25.0.1364.43
    cpe:2.3:a:google:chrome:25.0.1364.43
  • Google Chrome 25.0.1364.44
    cpe:2.3:a:google:chrome:25.0.1364.44
  • Google Chrome 25.0.1364.41
    cpe:2.3:a:google:chrome:25.0.1364.41
  • Google Chrome 25.0.1364.42
    cpe:2.3:a:google:chrome:25.0.1364.42
  • Google Chrome 25.0.1364.47
    cpe:2.3:a:google:chrome:25.0.1364.47
  • Google Chrome 25.0.1364.48
    cpe:2.3:a:google:chrome:25.0.1364.48
  • Google Chrome 25.0.1364.45
    cpe:2.3:a:google:chrome:25.0.1364.45
  • Google Chrome 25.0.1364.46
    cpe:2.3:a:google:chrome:25.0.1364.46
  • Google Chrome 25.0.1364.52
    cpe:2.3:a:google:chrome:25.0.1364.52
  • Google Chrome 25.0.1364.51
    cpe:2.3:a:google:chrome:25.0.1364.51
  • Google Chrome 25.0.1364.50
    cpe:2.3:a:google:chrome:25.0.1364.50
  • Google Chrome 25.0.1364.49
    cpe:2.3:a:google:chrome:25.0.1364.49
  • Google Chrome 25.0.1364.56
    cpe:2.3:a:google:chrome:25.0.1364.56
  • Google Chrome 25.0.1364.55
    cpe:2.3:a:google:chrome:25.0.1364.55
  • Google Chrome 25.0.1364.54
    cpe:2.3:a:google:chrome:25.0.1364.54
  • Google Chrome 25.0.1364.53
    cpe:2.3:a:google:chrome:25.0.1364.53
  • Google Chrome 25.0.1364.62
    cpe:2.3:a:google:chrome:25.0.1364.62
  • Google Chrome 25.0.1364.61
    cpe:2.3:a:google:chrome:25.0.1364.61
  • Google Chrome 25.0.1364.58
    cpe:2.3:a:google:chrome:25.0.1364.58
  • Google Chrome 25.0.1364.57
    cpe:2.3:a:google:chrome:25.0.1364.57
  • Google Chrome 25.0.1364.67
    cpe:2.3:a:google:chrome:25.0.1364.67
  • Google Chrome 25.0.1364.66
    cpe:2.3:a:google:chrome:25.0.1364.66
  • Google Chrome 25.0.1364.65
    cpe:2.3:a:google:chrome:25.0.1364.65
  • Google Chrome 25.0.1364.63
    cpe:2.3:a:google:chrome:25.0.1364.63
  • Google Chrome 25.0.1364.0
    cpe:2.3:a:google:chrome:25.0.1364.0
  • Google Chrome 25.0.1364.1
    cpe:2.3:a:google:chrome:25.0.1364.1
  • Google Chrome 25.0.1364.2
    cpe:2.3:a:google:chrome:25.0.1364.2
  • Google Chrome 25.0.1364.3
    cpe:2.3:a:google:chrome:25.0.1364.3
  • Google Chrome 25.0.1364.5
    cpe:2.3:a:google:chrome:25.0.1364.5
  • Google Chrome 25.0.1364.7
    cpe:2.3:a:google:chrome:25.0.1364.7
  • Google Chrome 25.0.1364.8
    cpe:2.3:a:google:chrome:25.0.1364.8
  • Google Chrome 25.0.1364.9
    cpe:2.3:a:google:chrome:25.0.1364.9
  • Google Chrome 25.0.1364.10
    cpe:2.3:a:google:chrome:25.0.1364.10
  • Google Chrome 25.0.1364.11
    cpe:2.3:a:google:chrome:25.0.1364.11
  • Google Chrome 25.0.1364.12
    cpe:2.3:a:google:chrome:25.0.1364.12
  • Google Chrome 25.0.1364.13
    cpe:2.3:a:google:chrome:25.0.1364.13
  • Google Chrome 25.0.1364.14
    cpe:2.3:a:google:chrome:25.0.1364.14
  • Google Chrome 25.0.1364.15
    cpe:2.3:a:google:chrome:25.0.1364.15
  • Google Chrome 25.0.1364.16
    cpe:2.3:a:google:chrome:25.0.1364.16
  • Google Chrome 25.0.1364.18
    cpe:2.3:a:google:chrome:25.0.1364.18
  • Google Chrome 25.0.1364.17
    cpe:2.3:a:google:chrome:25.0.1364.17
  • Google Chrome 25.0.1364.20
    cpe:2.3:a:google:chrome:25.0.1364.20
  • Google Chrome 25.0.1364.19
    cpe:2.3:a:google:chrome:25.0.1364.19
  • Google Chrome 25.0.1364.22
    cpe:2.3:a:google:chrome:25.0.1364.22
  • Google Chrome 25.0.1364.21
    cpe:2.3:a:google:chrome:25.0.1364.21
  • Google Chrome 25.0.1364.24
    cpe:2.3:a:google:chrome:25.0.1364.24
  • Google Chrome 25.0.1364.23
    cpe:2.3:a:google:chrome:25.0.1364.23
  • Google Chrome 25.0.1364.26
    cpe:2.3:a:google:chrome:25.0.1364.26
  • Google Chrome 25.0.1364.25
    cpe:2.3:a:google:chrome:25.0.1364.25
  • Google Chrome 25.0.1364.28
    cpe:2.3:a:google:chrome:25.0.1364.28
  • Google Chrome 25.0.1364.27
    cpe:2.3:a:google:chrome:25.0.1364.27
  • Google Chrome 25.0.1364.30
    cpe:2.3:a:google:chrome:25.0.1364.30
  • Google Chrome 25.0.1364.29
    cpe:2.3:a:google:chrome:25.0.1364.29
  • Google Chrome 25.0.1364.32
    cpe:2.3:a:google:chrome:25.0.1364.32
  • Google Chrome 25.0.1364.31
    cpe:2.3:a:google:chrome:25.0.1364.31
  • Google Chrome 25.0.1364.74
    cpe:2.3:a:google:chrome:25.0.1364.74
  • Google Chrome 25.0.1364.75
    cpe:2.3:a:google:chrome:25.0.1364.75
  • Google Chrome 25.0.1364.76
    cpe:2.3:a:google:chrome:25.0.1364.76
  • Google Chrome 25.0.1364.77
    cpe:2.3:a:google:chrome:25.0.1364.77
  • Google Chrome 25.0.1364.68
    cpe:2.3:a:google:chrome:25.0.1364.68
  • Google Chrome 25.0.1364.70
    cpe:2.3:a:google:chrome:25.0.1364.70
  • Google Chrome 25.0.1364.72
    cpe:2.3:a:google:chrome:25.0.1364.72
  • Google Chrome 25.0.1364.73
    cpe:2.3:a:google:chrome:25.0.1364.73
  • Google Chrome 25.0.1364.82
    cpe:2.3:a:google:chrome:25.0.1364.82
  • Google Chrome 25.0.1364.84
    cpe:2.3:a:google:chrome:25.0.1364.84
  • Google Chrome 25.0.1364.85
    cpe:2.3:a:google:chrome:25.0.1364.85
  • Google Chrome 25.0.1364.86
    cpe:2.3:a:google:chrome:25.0.1364.86
  • Google Chrome 25.0.1364.78
    cpe:2.3:a:google:chrome:25.0.1364.78
  • Google Chrome 25.0.1364.79
    cpe:2.3:a:google:chrome:25.0.1364.79
  • Google Chrome 25.0.1364.80
    cpe:2.3:a:google:chrome:25.0.1364.80
  • Google Chrome 25.0.1364.81
    cpe:2.3:a:google:chrome:25.0.1364.81
  • Google Chrome 25.0.1364.92
    cpe:2.3:a:google:chrome:25.0.1364.92
  • Google Chrome 25.0.1364.91
    cpe:2.3:a:google:chrome:25.0.1364.91
  • Google Chrome 25.0.1364.93
    cpe:2.3:a:google:chrome:25.0.1364.93
  • Google Chrome 25.0.1364.88
    cpe:2.3:a:google:chrome:25.0.1364.88
  • Google Chrome 25.0.1364.87
    cpe:2.3:a:google:chrome:25.0.1364.87
  • Google Chrome 25.0.1364.90
    cpe:2.3:a:google:chrome:25.0.1364.90
  • Google Chrome 25.0.1364.89
    cpe:2.3:a:google:chrome:25.0.1364.89
  • Google Chrome 25.0.1364.95
    cpe:2.3:a:google:chrome:25.0.1364.95
  • Google Chrome 25.0.1364.98
    cpe:2.3:a:google:chrome:25.0.1364.98
  • Apple Mac OS X
    cpe:2.3:o:apple:mac_os_x
CVSS
Base: 7.5 (as of 16-11-2016 - 12:35)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Windows
    NASL id GOOGLE_CHROME_25_0_1364_97.NASL
    description The version of Google Chrome installed on the remote host is a version prior to 25.0.1364.97. It is, therefore, affected by the following vulnerabilities : - An unspecified memory corruption error exists related to 'web audio node'. (CVE-2013-0879) - Use-after-free errors exist related to database and URL handling. (CVE-2013-0880, CVE-2013-0898) - Improper memory read errors exist related to Matroska, excessive SVG parameters, and Skia. (CVE-2013-0881, CVE-2013-0882, CVE-2013-0883, CVE-2013-0888) - An error exists related to improper loading of 'NaCl'. (CVE-2013-0884) - The 'web store' is granted too many API permissions. (CVE-2013-0885) - The developer tools process is granted too many permissions and trusts remote servers incorrectly. (CVE-2013-0887) - User gestures are not properly checked with respect to dangerous file downloads. (CVE-2013-0889) - An unspecified memory safety issue exists in the IPC layer. (CVE-2013-0890) - Integer overflow errors exist related to blob and 'Opus' handling. (CVE-2013-0891, CVE-2013-0899) - Numerous, unspecified, lower-severity issues exist related to the IPC layer. (CVE-2013-0892) - Race conditions exist related to media handling and ICU. (CVE-2013-0893, CVE-2013-0900) - A buffer overflow exists related to vorbis decoding. (CVE-2013-0894) - Memory management errors exist related to plugin message handling. (CVE-2013-0896) - An off-by-one read error exists related to PDF handling. (CVE-2013-0897) Note that the vendor states that WebKit's MathML implementation has been disabled in this release. This is due to several unspecified, high severity security issues. 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 64813
    published 2013-02-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=64813
    title Google Chrome < 25.0.1364.97 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
    source https://www.tenable.com/plugins/index.php?view=single&id=70112
    title GLSA-201309-16 : Chromium, V8: Multiple vulnerabilities
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_DFD92CB27D4811E2AD4800262D5ED8EE.NASL
    description Google Chrome Releases reports : [172243] High CVE-2013-0879: Memory corruption with web audio node. Credit to Atte Kettunen of OUSPG. [171951] High CVE-2013-0880: Use-after-free in database handling. Credit to Chamal de Silva. [167069] Medium CVE-2013-0881: Bad read in Matroska handling. Credit to Atte Kettunen of OUSPG. [165432] High CVE-2013-0882: Bad memory access with excessive SVG parameters. Credit to Renata Hodovan. [142169] Medium CVE-2013-0883: Bad read in Skia. Credit to Atte Kettunen of OUSPG. [172984] Low CVE-2013-0884: Inappropriate load of NaCl. Credit to Google Chrome Security Team (Chris Evans). [172369] Medium CVE-2013-0885: Too many API permissions granted to web store. [171065] [170836] Low CVE-2013-0887: Developer tools process has too many permissions and places too much trust in the connected server. [170666] Medium CVE-2013-0888: Out-of-bounds read in Skia. Credit to Google Chrome Security Team (Inferno). [170569] Low CVE-2013-0889: Tighten user gesture check for dangerous file downloads. [169973] [169966] High CVE-2013-0890: Memory safety issues across the IPC layer. Credit to Google Chrome Security Team (Chris Evans). [169685] High CVE-2013-0891: Integer overflow in blob handling. Credit to Google Chrome Security Team (Juri Aedla). [169295] [168710] [166493] [165836] [165747] [164958] [164946] Medium CVE-2013-0892: Lower severity issues across the IPC layer. Credit to Google Chrome Security Team (Chris Evans). [168570] Medium CVE-2013-0893: Race condition in media handling. Credit to Andrew Scherkus of the Chromium development community. [168473] High CVE-2013-0894: Buffer overflow in vorbis decoding. Credit to Google Chrome Security Team (Inferno). [Linux / Mac] [167840] High CVE-2013-0895: Incorrect path handling in file copying. Credit to Google Chrome Security Team (Juri Aedla). [166708] High CVE-2013-0896: Memory management issues in plug-in message handling. Credit to Google Chrome Security Team (Cris Neckar). [165537] Low CVE-2013-0897: Off-by-one read in PDF. Credit to Mateusz Jurczyk, with contributions by Gynvael Coldwind, both from Google Security Team. [164643] High CVE-2013-0898: Use-after-free in URL handling. Credit to Alexander Potapenko of the Chromium development community. [160480] Low CVE-2013-0899: Integer overflow in Opus handling. Credit to Google Chrome Security Team (Juri Aedla). [152442] Medium CVE-2013-0900: Race condition in ICU. Credit to Google Chrome Security Team (Inferno).
    last seen 2019-02-21
    modified 2016-05-26
    plugin id 64859
    published 2013-02-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=64859
    title FreeBSD : chromium -- multiple vulnerabilities (dfd92cb2-7d48-11e2-ad48-00262d5ed8ee)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2013-203.NASL
    description chromium was updated to version 27.0.1425 having both stability and security fixes : - Bug and stability fixes : - Fixed crash after clicking through malware warning. (Issue: 173986) - Fixed broken command line to create extensions with locale info (Issue: 176187) - Hosted apps in Chrome will always be opened from app launcher. (Issue: 176267) - Added modal confirmation dialog to the enterprise profile sign-in flow. (Issue: 171236) - Fixed a crash with autofill. (Issues: 175454, 176576) - Fixed issues with sign-in. (Issues: 175672, 175819, 175541, 176190) - Fixed spurious profile shortcuts created with a system-level install. (Issue: 177047) - Fixed the background tab flashing with certain themes. (Issue: 175426) - Security Fixes: (bnc#804986) - High CVE-2013-0879: Memory corruption with web audio node - High CVE-2013-0880: Use-after-free in database handling - Medium CVE-2013-0881: Bad read in Matroska handling - High CVE-2013-0882: Bad memory access with excessive SVG parameters. - Medium CVE-2013-0883: Bad read in Skia. - Low CVE-2013-0884: Inappropriate load of NaCl. - Medium CVE-2013-0885: Too many API permissions granted to web store - Medium CVE-2013-0886: Incorrect NaCl signal handling. - Low CVE-2013-0887: Developer tools process has too many permissions and places too much trust in the connected server - Medium CVE-2013-0888: Out-of-bounds read in Skia - Low CVE-2013-0889: Tighten user gesture check for dangerous file downloads. - High CVE-2013-0890: Memory safety issues across the IPC layer. - High CVE-2013-0891: Integer overflow in blob handling. - Medium CVE-2013-0892: Lower severity issues across the IPC layer - Medium CVE-2013-0893: Race condition in media handling. - High CVE-2013-0894: Buffer overflow in vorbis decoding. - High CVE-2013-0895: Incorrect path handling in file copying. - High CVE-2013-0896: Memory management issues in plug-in message handling - Low CVE-2013-0897: Off-by-one read in PDF - High CVE-2013-0898: Use-after-free in URL handling - Low CVE-2013-0899: Integer overflow in Opus handling - Medium CVE-2013-0900: Race condition in ICU - Make adjustment for autodetecting of the PepperFlash library. The package with the PepperFlash hopefully will be soon available through packman - Update to 26.0.1411 - Bug and stability fixes - Update to 26.0.1403 - Bug and stability fixes - Using system libxml2 requires system libxslt. - Using system MESA does not work in i586 for some reason. - Also use system MESA, factory version seems adecuate now. - Always use system libxml2. - Restrict the usage of system libraries instead of the bundled ones to new products, too much hassle otherwise. - Also link kerberos and libgps directly, do not dlopen them. - Avoid using dlopen on system libraries, rpm or the package Manager do not handle this at all. tested for a few weeks and implemented with a macro so it can be easily disabled if problems arise. - Use SOME system libraries instead of the bundled ones, tested for several weeks and implemented with a macro for easy enable/Disable in case of trouble. - Update to 26.0.1393 - Bug and stability fixes - Security fixes - Update to 26.0.1375 - Bug and stability fixes - Update to 26.0.1371 - Bug and stability fixes - Update to 26.0.1367 - Bug and stability fixes
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74920
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74920
    title openSUSE Security Update : chromium (openSUSE-SU-2013:0454-1)
oval via4
accepted 2013-08-12T04:08:01.480-04:00
class vulnerability
contributors
  • name Shane Shaffer
    organization G2, Inc.
  • name Jonathan Baker
    organization The MITRE Corporation
  • name Maria Kedovskaya
    organization ALTX-SOFT
definition_extensions
comment Google Chrome is installed
oval oval:org.mitre.oval:def:11914
description The developer-tools process in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, does not properly restrict privileges during interaction with a connected server, which has unspecified impact and attack vectors.
family windows
id oval:org.mitre.oval:def:15788
status accepted
submitted 2013-02-24T15:45:10.582-05:00
title The developer-tools process in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, does not properly restrict privileges during interaction with a connected server
version 44
refmap via4
confirm
suse openSUSE-SU-2013:0454
Last major update 02-11-2013 - 23:30
Published 23-02-2013 - 16:55
Last modified 18-09-2017 - 21:35
Back to Top