ID CVE-2013-0890
Summary Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service (memory corruption) or possibly have other impact via unknown vectors.
References
Vulnerable Configurations
  • 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.17
    cpe:2.3:a:google:chrome:25.0.1364.17
  • Google Chrome 25.0.1364.18
    cpe:2.3:a:google:chrome:25.0.1364.18
  • Google Chrome 25.0.1364.19
    cpe:2.3:a:google:chrome:25.0.1364.19
  • Google Chrome 25.0.1364.20
    cpe:2.3:a:google:chrome:25.0.1364.20
  • Google Chrome 25.0.1364.21
    cpe:2.3:a:google:chrome:25.0.1364.21
  • Google Chrome 25.0.1364.22
    cpe:2.3:a:google:chrome:25.0.1364.22
  • Google Chrome 25.0.1364.23
    cpe:2.3:a:google:chrome:25.0.1364.23
  • Google Chrome 25.0.1364.24
    cpe:2.3:a:google:chrome:25.0.1364.24
  • Google Chrome 25.0.1364.25
    cpe:2.3:a:google:chrome:25.0.1364.25
  • Google Chrome 25.0.1364.26
    cpe:2.3:a:google:chrome:25.0.1364.26
  • Google Chrome 25.0.1364.27
    cpe:2.3:a:google:chrome:25.0.1364.27
  • Google Chrome 25.0.1364.28
    cpe:2.3:a:google:chrome:25.0.1364.28
  • Google Chrome 25.0.1364.29
    cpe:2.3:a:google:chrome:25.0.1364.29
  • Google Chrome 25.0.1364.30
    cpe:2.3:a:google:chrome:25.0.1364.30
  • Google Chrome 25.0.1364.31
    cpe:2.3:a:google:chrome:25.0.1364.31
  • Google Chrome 25.0.1364.32
    cpe:2.3:a:google:chrome:25.0.1364.32
  • 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.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.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.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.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.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.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.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.49
    cpe:2.3:a:google:chrome:25.0.1364.49
  • Google Chrome 25.0.1364.50
    cpe:2.3:a:google:chrome:25.0.1364.50
  • Google Chrome 25.0.1364.51
    cpe:2.3:a:google:chrome:25.0.1364.51
  • Google Chrome 25.0.1364.52
    cpe:2.3:a:google:chrome:25.0.1364.52
  • Google Chrome 25.0.1364.53
    cpe:2.3:a:google:chrome:25.0.1364.53
  • Google Chrome 25.0.1364.54
    cpe:2.3:a:google:chrome:25.0.1364.54
  • Google Chrome 25.0.1364.55
    cpe:2.3:a:google:chrome:25.0.1364.55
  • Google Chrome 25.0.1364.56
    cpe:2.3:a:google:chrome:25.0.1364.56
  • Google Chrome 25.0.1364.57
    cpe:2.3:a:google:chrome:25.0.1364.57
  • Google Chrome 25.0.1364.58
    cpe:2.3:a:google:chrome:25.0.1364.58
  • Google Chrome 25.0.1364.61
    cpe:2.3:a:google:chrome:25.0.1364.61
  • Google Chrome 25.0.1364.62
    cpe:2.3:a:google:chrome:25.0.1364.62
  • Google Chrome 25.0.1364.63
    cpe:2.3:a:google:chrome:25.0.1364.63
  • Google Chrome 25.0.1364.65
    cpe:2.3:a:google:chrome:25.0.1364.65
  • Google Chrome 25.0.1364.66
    cpe:2.3:a:google:chrome:25.0.1364.66
  • Google Chrome 25.0.1364.67
    cpe:2.3:a:google:chrome:25.0.1364.67
  • 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.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.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.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.87
    cpe:2.3:a:google:chrome:25.0.1364.87
  • Google Chrome 25.0.1364.88
    cpe:2.3:a:google:chrome:25.0.1364.88
  • Google Chrome 25.0.1364.89
    cpe:2.3:a:google:chrome:25.0.1364.89
  • Google Chrome 25.0.1364.90
    cpe:2.3:a:google:chrome:25.0.1364.90
  • Google Chrome 25.0.1364.91
    cpe:2.3:a:google:chrome:25.0.1364.91
  • Google Chrome 25.0.1364.92
    cpe:2.3:a:google:chrome:25.0.1364.92
  • Google Chrome 25.0.1364.93
    cpe:2.3:a:google:chrome:25.0.1364.93
  • 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
  • OpenSUSE 12.1
    cpe:2.3:o:opensuse:opensuse:12.1
  • OpenSUSE 12.2
    cpe:2.3:o:opensuse:opensuse:12.2
  • 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.17
    cpe:2.3:a:google:chrome:25.0.1364.17
  • Google Chrome 25.0.1364.18
    cpe:2.3:a:google:chrome:25.0.1364.18
  • Google Chrome 25.0.1364.19
    cpe:2.3:a:google:chrome:25.0.1364.19
  • Google Chrome 25.0.1364.20
    cpe:2.3:a:google:chrome:25.0.1364.20
  • Google Chrome 25.0.1364.21
    cpe:2.3:a:google:chrome:25.0.1364.21
  • Google Chrome 25.0.1364.22
    cpe:2.3:a:google:chrome:25.0.1364.22
  • Google Chrome 25.0.1364.23
    cpe:2.3:a:google:chrome:25.0.1364.23
  • Google Chrome 25.0.1364.24
    cpe:2.3:a:google:chrome:25.0.1364.24
  • Google Chrome 25.0.1364.25
    cpe:2.3:a:google:chrome:25.0.1364.25
  • Google Chrome 25.0.1364.26
    cpe:2.3:a:google:chrome:25.0.1364.26
  • Google Chrome 25.0.1364.27
    cpe:2.3:a:google:chrome:25.0.1364.27
  • Google Chrome 25.0.1364.28
    cpe:2.3:a:google:chrome:25.0.1364.28
  • Google Chrome 25.0.1364.29
    cpe:2.3:a:google:chrome:25.0.1364.29
  • Google Chrome 25.0.1364.30
    cpe:2.3:a:google:chrome:25.0.1364.30
  • Google Chrome 25.0.1364.31
    cpe:2.3:a:google:chrome:25.0.1364.31
  • Google Chrome 25.0.1364.32
    cpe:2.3:a:google:chrome:25.0.1364.32
  • 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.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.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.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.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.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.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.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.49
    cpe:2.3:a:google:chrome:25.0.1364.49
  • Google Chrome 25.0.1364.50
    cpe:2.3:a:google:chrome:25.0.1364.50
  • Google Chrome 25.0.1364.51
    cpe:2.3:a:google:chrome:25.0.1364.51
  • Google Chrome 25.0.1364.52
    cpe:2.3:a:google:chrome:25.0.1364.52
  • Google Chrome 25.0.1364.53
    cpe:2.3:a:google:chrome:25.0.1364.53
  • Google Chrome 25.0.1364.54
    cpe:2.3:a:google:chrome:25.0.1364.54
  • Google Chrome 25.0.1364.55
    cpe:2.3:a:google:chrome:25.0.1364.55
  • Google Chrome 25.0.1364.56
    cpe:2.3:a:google:chrome:25.0.1364.56
  • Google Chrome 25.0.1364.57
    cpe:2.3:a:google:chrome:25.0.1364.57
  • Google Chrome 25.0.1364.58
    cpe:2.3:a:google:chrome:25.0.1364.58
  • Google Chrome 25.0.1364.61
    cpe:2.3:a:google:chrome:25.0.1364.61
  • Google Chrome 25.0.1364.62
    cpe:2.3:a:google:chrome:25.0.1364.62
  • Google Chrome 25.0.1364.63
    cpe:2.3:a:google:chrome:25.0.1364.63
  • Google Chrome 25.0.1364.65
    cpe:2.3:a:google:chrome:25.0.1364.65
  • Google Chrome 25.0.1364.66
    cpe:2.3:a:google:chrome:25.0.1364.66
  • Google Chrome 25.0.1364.67
    cpe:2.3:a:google:chrome:25.0.1364.67
  • 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.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.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.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.87
    cpe:2.3:a:google:chrome:25.0.1364.87
  • Google Chrome 25.0.1364.88
    cpe:2.3:a:google:chrome:25.0.1364.88
  • Google Chrome 25.0.1364.89
    cpe:2.3:a:google:chrome:25.0.1364.89
  • Google Chrome 25.0.1364.90
    cpe:2.3:a:google:chrome:25.0.1364.90
  • Google Chrome 25.0.1364.91
    cpe:2.3:a:google:chrome:25.0.1364.91
  • Google Chrome 25.0.1364.92
    cpe:2.3:a:google:chrome:25.0.1364.92
  • Google Chrome 25.0.1364.93
    cpe:2.3:a:google:chrome:25.0.1364.93
  • Google Chrome 25.0.1364.95
    cpe:2.3:a:google:chrome:25.0.1364.95
  • Linux Kernel
    cpe:2.3:o:linux:linux_kernel
  • Microsoft Windows
    cpe:2.3:o:microsoft:windows
CVSS
Base: 7.5 (as of 13-10-2016 - 09:55)
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
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:17.959-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 Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service (memory corruption) or possibly have other impact via unknown vectors.
family windows
id oval:org.mitre.oval:def:16208
status accepted
submitted 2013-02-24T15:45:10.582-05:00
title Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service (memory corruption) or possibly have other impact via unknown vectors
version 44
refmap via4
confirm
suse openSUSE-SU-2013:0454
Last major update 13-10-2016 - 11:13
Published 23-02-2013 - 16:55
Last modified 30-10-2018 - 12:27
Back to Top