ID CVE-2013-2919
Summary Google V8, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
References
Vulnerable Configurations
  • OpenSUSE 12.2
    cpe:2.3:o:opensuse:opensuse:12.2
  • OpenSUSE 12.3
    cpe:2.3:o:opensuse:opensuse:12.3
  • OpenSUSE 13.1
    cpe:2.3:o:opensuse:opensuse:13.1
  • Google Chrome 30.0.1599.0
    cpe:2.3:a:google:chrome:30.0.1599.0
  • Google Chrome 30.0.1599.1
    cpe:2.3:a:google:chrome:30.0.1599.1
  • Google Chrome 30.0.1599.2
    cpe:2.3:a:google:chrome:30.0.1599.2
  • Google Chrome 30.0.1599.4
    cpe:2.3:a:google:chrome:30.0.1599.4
  • Google Chrome 30.0.1599.5
    cpe:2.3:a:google:chrome:30.0.1599.5
  • Google Chrome 30.0.1599.6
    cpe:2.3:a:google:chrome:30.0.1599.6
  • Google Chrome 30.0.1599.7
    cpe:2.3:a:google:chrome:30.0.1599.7
  • Google Chrome 30.0.1599.8
    cpe:2.3:a:google:chrome:30.0.1599.8
  • Google Chrome 30.0.1599.9
    cpe:2.3:a:google:chrome:30.0.1599.9
  • Google Chrome 30.0.1599.10
    cpe:2.3:a:google:chrome:30.0.1599.10
  • Google Chrome 30.0.1599.11
    cpe:2.3:a:google:chrome:30.0.1599.11
  • Google Chrome 30.0.1599.12
    cpe:2.3:a:google:chrome:30.0.1599.12
  • Google Chrome 30.0.1599.13
    cpe:2.3:a:google:chrome:30.0.1599.13
  • Google Chrome 30.0.1599.14
    cpe:2.3:a:google:chrome:30.0.1599.14
  • Google Chrome 30.0.1599.15
    cpe:2.3:a:google:chrome:30.0.1599.15
  • Google Chrome 30.0.1599.16
    cpe:2.3:a:google:chrome:30.0.1599.16
  • Google Chrome 30.0.1599.17
    cpe:2.3:a:google:chrome:30.0.1599.17
  • Google Chrome 30.0.1599.18
    cpe:2.3:a:google:chrome:30.0.1599.18
  • Google Chrome 30.0.1599.19
    cpe:2.3:a:google:chrome:30.0.1599.19
  • Google Chrome 30.0.1599.20
    cpe:2.3:a:google:chrome:30.0.1599.20
  • Google Chrome 30.0.1599.21
    cpe:2.3:a:google:chrome:30.0.1599.21
  • Google Chrome 30.0.1599.22
    cpe:2.3:a:google:chrome:30.0.1599.22
  • Google Chrome 30.0.1599.23
    cpe:2.3:a:google:chrome:30.0.1599.23
  • Google Chrome 30.0.1599.24
    cpe:2.3:a:google:chrome:30.0.1599.24
  • Google Chrome 30.0.1599.25
    cpe:2.3:a:google:chrome:30.0.1599.25
  • Google Chrome 30.0.1599.26
    cpe:2.3:a:google:chrome:30.0.1599.26
  • Google Chrome 30.0.1599.27
    cpe:2.3:a:google:chrome:30.0.1599.27
  • Google Chrome 30.0.1599.28
    cpe:2.3:a:google:chrome:30.0.1599.28
  • Google Chrome 30.0.1599.29
    cpe:2.3:a:google:chrome:30.0.1599.29
  • Google Chrome 30.0.1599.30
    cpe:2.3:a:google:chrome:30.0.1599.30
  • Google Chrome 30.0.1599.31
    cpe:2.3:a:google:chrome:30.0.1599.31
  • Google Chrome 30.0.1599.32
    cpe:2.3:a:google:chrome:30.0.1599.32
  • Google Chrome 30.0.1599.33
    cpe:2.3:a:google:chrome:30.0.1599.33
  • Google Chrome 30.0.1599.34
    cpe:2.3:a:google:chrome:30.0.1599.34
  • Google Chrome 30.0.1599.35
    cpe:2.3:a:google:chrome:30.0.1599.35
  • Google Chrome 30.0.1599.36
    cpe:2.3:a:google:chrome:30.0.1599.36
  • Google Chrome 30.0.1599.37
    cpe:2.3:a:google:chrome:30.0.1599.37
  • Google Chrome 30.0.1599.38
    cpe:2.3:a:google:chrome:30.0.1599.38
  • Google Chrome 30.0.1599.39
    cpe:2.3:a:google:chrome:30.0.1599.39
  • Google Chrome 30.0.1599.40
    cpe:2.3:a:google:chrome:30.0.1599.40
  • Google Chrome 30.0.1599.41
    cpe:2.3:a:google:chrome:30.0.1599.41
  • Google Chrome 30.0.1599.42
    cpe:2.3:a:google:chrome:30.0.1599.42
  • Google Chrome 30.0.1599.43
    cpe:2.3:a:google:chrome:30.0.1599.43
  • Google Chrome 30.0.1599.44
    cpe:2.3:a:google:chrome:30.0.1599.44
  • Google Chrome 30.0.1599.47
    cpe:2.3:a:google:chrome:30.0.1599.47
  • Google Chrome 30.0.1599.48
    cpe:2.3:a:google:chrome:30.0.1599.48
  • Google Chrome 30.0.1599.49
    cpe:2.3:a:google:chrome:30.0.1599.49
  • Google Chrome 30.0.1599.50
    cpe:2.3:a:google:chrome:30.0.1599.50
  • Google Chrome 30.0.1599.51
    cpe:2.3:a:google:chrome:30.0.1599.51
  • Google Chrome 30.0.1599.52
    cpe:2.3:a:google:chrome:30.0.1599.52
  • Google Chrome 30.0.1599.53
    cpe:2.3:a:google:chrome:30.0.1599.53
  • Google Chrome 30.0.1599.56
    cpe:2.3:a:google:chrome:30.0.1599.56
  • Google Chrome 30.0.1599.57
    cpe:2.3:a:google:chrome:30.0.1599.57
  • Google Chrome 30.0.1599.58
    cpe:2.3:a:google:chrome:30.0.1599.58
  • Google Chrome 30.0.1599.59
    cpe:2.3:a:google:chrome:30.0.1599.59
  • Google Chrome 30.0.1599.60
    cpe:2.3:a:google:chrome:30.0.1599.60
  • Google Chrome 30.0.1599.61
    cpe:2.3:a:google:chrome:30.0.1599.61
  • Google Chrome 30.0.1599.64
    cpe:2.3:a:google:chrome:30.0.1599.64
  • Google Chrome 30.0.1599.65
    cpe:2.3:a:google:chrome:30.0.1599.65
  • Debian Linux 7.0
    cpe:2.3:o:debian:debian_linux:7.0
  • Debian Linux 8.0 (Jessie)
    cpe:2.3:o:debian:debian_linux:8.0
CVSS
Base: 7.5 (as of 08-09-2016 - 21:47)
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 SuSE Local Security Checks
    NASL id OPENSUSE-2013-961.NASL
    description Chromium was updated to 31.0.1650.57: Stable channel update : - Security Fixes : - CVE-2013-6632: Multiple memory corruption issues. - Update to Chromium 31.0.1650.48 Stable Channel update : - Security fixes : - CVE-2013-6621: Use after free related to speech input elements.. - CVE-2013-6622: Use after free related to media elements. - CVE-2013-6623: Out of bounds read in SVG. - CVE-2013-6624: Use after free related to “id” attribute strings. - CVE-2013-6625: Use after free in DOM ranges. - CVE-2013-6626: Address bar spoofing related to interstitial warnings. - CVE-2013-6627: Out of bounds read in HTTP parsing. - CVE-2013-6628: Issue with certificates not being checked during TLS renegotiation. - CVE-2013-2931: Various fixes from internal audits, fuzzing and other initiatives. - CVE-2013-6629: Read of uninitialized memory in libjpeg and libjpeg-turbo. - CVE-2013-6630: Read of uninitialized memory in libjpeg-turbo. - CVE-2013-6631: Use after free in libjingle. - Added patch chromium-fix-chromedriver-build.diff to fix the chromedriver build - Enable ARM build for Chromium. - Added patches chromium-arm-webrtc-fix.patch, chromium-fix-arm-icu.patch and chromium-fix-arm-sysroot.patch to resolve ARM specific build issues - Update to Chromium 30.0.1599.114 Stable Channel update: fix build for 32bit systems - Drop patch chromium-fix-chromedriver-build.diff. This is now fixed upstream - For openSUSE versions lower than 13.1, build against the in-tree libicu - Update to Chromium 30.0.1599.101 - Security Fixes : + CVE-2013-2925: Use after free in XHR + CVE-2013-2926: Use after free in editing + CVE-2013-2927: Use after free in forms. + CVE-2013-2928: Various fixes from internal audits, fuzzing and other initiatives. - Update to Chromium 30.0.1599.66 - Easier searching by image - A number of new apps/extension APIs - Lots of under the hood changes for stability and performance - Security fixes : + CVE-2013-2906: Races in Web Audio + CVE-2013-2907: Out of bounds read in Window.prototype object + CVE-2013-2908: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2909: Use after free in inline-block rendering + CVE-2013-2910: Use-after-free in Web Audio + CVE-2013-2911: Use-after-free in XSLT + CVE-2013-2912: Use-after-free in PPAPI + CVE-2013-2913: Use-after-free in XML document parsing + CVE-2013-2914: Use after free in the Windows color chooser dialog + CVE-2013-2915: Address bar spoofing via a malformed scheme + CVE-2013-2916: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2917: Out of bounds read in Web Audio + CVE-2013-2918: Use-after-free in DOM + CVE-2013-2919: Memory corruption in V8 + CVE-2013-2920: Out of bounds read in URL parsing + CVE-2013-2921: Use-after-free in resource loader + CVE-2013-2922: Use-after-free in template element + CVE-2013-2923: Various fixes from internal audits, fuzzing and other initiatives + CVE-2013-2924: Use-after-free in ICU. Upstream bug
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75225
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75225
    title openSUSE Security Update : chromium (openSUSE-SU-2013:1861-1)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2014-37.NASL
    description - Update to Chromium 31.0.1650.63 Stable channel update : - Security fixes : - CVE-2013-6634: Session fixation in sync related to 302 redirects - CVE-2013-6635: Use-after-free in editing - CVE-2013-6636: Address bar spoofing related to modal dialogs - CVE-2013-6637: Various fixes from internal audits, fuzzing and other initiatives. - CVE-2013-6638: Buffer overflow in v8 - CVE-2013-6639: Out of bounds write in v8. - CVE-2013-6640: Out of bounds read in v8 - and 12 other security fixes. - Remove the build flags to build according to the Chrome ffmpeg branding and the proprietary codecs. (bnc#847971) - Update to Chromium 31.0.1650.57 Stable channel update : - Security Fixes : - CVE-2013-6632: Multiple memory corruption issues. - Update to Chromium 31.0.1650.48 Stable Channel update : - Security fixes : - CVE-2013-6621: Use after free related to speech input elements.. - CVE-2013-6622: Use after free related to media elements. - CVE-2013-6623: Out of bounds read in SVG. - CVE-2013-6624: Use after free related to “id” attribute strings. - CVE-2013-6625: Use after free in DOM ranges. - CVE-2013-6626: Address bar spoofing related to interstitial warnings. - CVE-2013-6627: Out of bounds read in HTTP parsing. - CVE-2013-6628: Issue with certificates not being checked during TLS renegotiation. - CVE-2013-2931: Various fixes from internal audits, fuzzing and other initiatives. - CVE-2013-6629: Read of uninitialized memory in libjpeg and libjpeg-turbo. - CVE-2013-6630: Read of uninitialized memory in libjpeg-turbo. - CVE-2013-6631: Use after free in libjingle. - Added patch chromium-fix-chromedriver-build.diff to fix the chromedriver build - Enable ARM build for Chromium. - Added patches chromium-arm-webrtc-fix.patch, chromium-fix-arm-icu.patch and chromium-fix-arm-sysroot.patch to resolve ARM specific build issues - Update to Chromium 30.0.1599.114 Stable Channel update: fix build for 32bit systems - Drop patch chromium-fix-chromedriver-build.diff. This is now fixed upstream - For openSUSE versions lower than 13.1, build against the in-tree libicu - Update to Chromium 30.0.1599.101 - Security Fixes : + CVE-2013-2925: Use after free in XHR + CVE-2013-2926: Use after free in editing + CVE-2013-2927: Use after free in forms. + CVE-2013-2928: Various fixes from internal audits, fuzzing and other initiatives. - Update to Chromium 30.0.1599.66 - Easier searching by image - A number of new apps/extension APIs - Lots of under the hood changes for stability and performance - Security fixes : + CVE-2013-2906: Races in Web Audio + CVE-2013-2907: Out of bounds read in Window.prototype object + CVE-2013-2908: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2909: Use after free in inline-block rendering + CVE-2013-2910: Use-after-free in Web Audio + CVE-2013-2911: Use-after-free in XSLT + CVE-2013-2912: Use-after-free in PPAPI + CVE-2013-2913: Use-after-free in XML document parsing + CVE-2013-2914: Use after free in the Windows color chooser dialog + CVE-2013-2915: Address bar spoofing via a malformed scheme + CVE-2013-2916: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2917: Out of bounds read in Web Audio + CVE-2013-2918: Use-after-free in DOM + CVE-2013-2919: Memory corruption in V8 + CVE-2013-2920: Out of bounds read in URL parsing + CVE-2013-2921: Use-after-free in resource loader + CVE-2013-2922: Use-after-free in template element + CVE-2013-2923: Various fixes from internal audits, fuzzing and other initiatives + CVE-2013-2924: Use-after-free in ICU. Upstream bug
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75366
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75366
    title openSUSE Security Update : chromium (openSUSE-SU-2014:0065-1)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201403-01.NASL
    description The remote host is affected by the vulnerability described in GLSA-201403-01 (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-10-29
    plugin id 72851
    published 2014-03-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=72851
    title GLSA-201403-01 : Chromium, V8: Multiple vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2013-769.NASL
    description Update to Chromium 30.0.1599.66 : - Easier searching by image - A number of new apps/extension APIs - Lots of under the hood changes for stability and performance - Security fixes : + CVE-2013-2906: Races in Web Audio + CVE-2013-2907: Out of bounds read in Window.prototype object + CVE-2013-2908: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2909: Use after free in inline-block rendering + CVE-2013-2910: Use-after-free in Web Audio + CVE-2013-2911: Use-after-free in XSLT + CVE-2013-2912: Use-after-free in PPAPI + CVE-2013-2913: Use-after-free in XML document parsing + CVE-2013-2914: Use after free in the Windows color chooser dialog + CVE-2013-2915: Address bar spoofing via a malformed scheme + CVE-2013-2916: Address bar spoofing related to the “204 No Content” status code + CVE-2013-2917: Out of bounds read in Web Audio + CVE-2013-2918: Use-after-free in DOM + CVE-2013-2919: Memory corruption in V8 + CVE-2013-2920: Out of bounds read in URL parsing + CVE-2013-2921: Use-after-free in resource loader + CVE-2013-2922: Use-after-free in template element + CVE-2013-2923: Various fixes from internal audits, fuzzing and other initiatives + CVE-2013-2924: Use-after-free in ICU. Upstream bug - Add patch chromium-fix-altgrkeys.diff - Make sure that AltGr is treated correctly (issue#296835) - Do not build with system libxml (bnc#825157) - Update to Chromium 31.0.1640.0 - Bug and Stability Fixes - Fix destkop file for chromium by removing extension from icon - Change the methodology for the Chromium packages. Build is now based on an official tarball. As soon as the Beta channel catches up with the current version, Chromium will be based on the Beta channel instead of svn snapshots - Update to 31.0.1632 - Bug and Stability fixes - Added the flag --enable-threaded-compositing to the startup script. This flag seems to be required when hardware acceleration is in use. This prevents websites from locking up on users in certain cases. - Update to 31.0.1627 - Bug and Stability fixes - Update to 31.0.1619 - bug and Stability fixes - require mozilla-nss-devel >= 3.14 and mozilla-nspr-devel >= 4.9.5 - Add patch exclude_ymp.diff to ensure that 1-click-install files are downloaded and NOT opened (bnc#836059) - Update to 31.0.1611 - Bug and stability fixes - Update to 31.0.1605 - Bug and stability fixes - Change the startup script so that Chromium will not start when the chrome_sandbox doesn't have the SETUID. (bnc#779448) - Update to 31.0.1601 - Bug and stability fixes - Update to 30.0.1594 - Bug and stability fixes - Correct specfile to properly own /usr/bin/chromium (bnc#831584) - Chromium now expects the SUID-helper installed in the same directory as chromium. So let's create a symlink to the helper in /usr/lib - Update to 30.0.1587 - Bug and stability fixes - Remove patch chromium-nss-compliant.diff (Upstream) - Update to 30.0.1575 - Bug and stability fixes - Enable the gpu-sandbox again due to upstream fix (chromium#255063) - Update to 30.0.1567 - bug and Stability fixes
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75170
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75170
    title openSUSE Security Update : chromium (openSUSE-SU-2013:1556-1)
  • NASL family Windows
    NASL id GOOGLE_CHROME_30_0_1599_66.NASL
    description The version of Google Chrome installed on the remote host is a version prior to 30.0.1599.66. It is, therefore, affected by multiple vulnerabilities : - A race condition exists related to 'Web Audio'. (CVE-2013-2906) - Out-of-bounds read errors exist related to the 'Window.prototype' object, 'Web Audio', and URL parsing. (CVE-2013-2907, CVE-2013-2917, CVE-2013-2920) - Several errors exist related to the address bar that could allow spoofing attacks. (CVE-2013-2908, CVE-2013-2915, CVE-2013-2916) - Use-after-free errors exist related to 'inline-block' rendering, 'Web Audio', XSLT, PPAPI, XML document parsing, Windows color chooser dialog, DOM, the resource loader, the 'template' element and ICU. (CVE-2013-2909, CVE-2013-2910, CVE-2013-2911, CVE-2013-2912, CVE-2013-2913, CVE-2013-2914, CVE-2013-2918, CVE-2013-2921, CVE-2013-2922, CVE-2013-2924) - A memory corruption error exists in the V8 JavaScript engine. (CVE-2013-2919) - Various, unspecified errors exist. (CVE-2013-2923)
    last seen 2019-02-21
    modified 2018-10-29
    plugin id 70273
    published 2013-10-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70273
    title Google Chrome < 30.0.1599.66 Multiple Vulnerabilities
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2785.NASL
    description Several vulnerabilities have been discovered in the chromium web browser. - CVE-2013-2906 Atte Kettunen of OUSPG discovered race conditions in Web Audio. - CVE-2013-2907 Boris Zbarsky discovered an out-of-bounds read in window.prototype. - CVE-2013-2908 Chamal de Silva discovered an address bar spoofing issue. - CVE-2013-2909 Atte Kuttenen of OUSPG discovered a use-after-free issue in inline-block. - CVE-2013-2910 Byoungyoung Lee of the Georgia Tech Information Security Center discovered a use-after-free issue in Web Audio. - CVE-2013-2911 Atte Kettunen of OUSPG discovered a use-after-free in Blink's XSLT handling. - CVE-2013-2912 Chamal de Silva and 41.w4r10r(at)garage4hackers.com discovered a use-after-free issue in the Pepper Plug-in API. - CVE-2013-2913 cloudfuzzer discovered a use-after-free issue in Blink's XML document parsing. - CVE-2013-2915 Wander Groeneveld discovered an address bar spoofing issue. - CVE-2013-2916 Masato Kinugawa discovered an address bar spoofing issue. - CVE-2013-2917 Byoungyoung Lee and Tielei Wang discovered an out-of-bounds read issue in Web Audio. - CVE-2013-2918 Byoungyoung Lee discoverd an out-of-bounds read in Blink's DOM implementation. - CVE-2013-2919 Adam Haile of Concrete Data discovered a memory corruption issue in the V8 JavaScript library. - CVE-2013-2920 Atte Kuttunen of OUSPG discovered an out-of-bounds read in URL host resolving. - CVE-2013-2921 Byoungyoung Lee and Tielei Wang discovered a use-after-free issue in resource loading. - CVE-2013-2922 Jon Butler discovered a use-after-free issue in Blink's HTML template element implementation. - CVE-2013-2924 A use-after-free issue was discovered in the International Components for Unicode (ICU) library. - CVE-2013-2925 Atte Kettunen of OUSPG discover a use-after-free issue in Blink's XML HTTP request implementation. - CVE-2013-2926 cloudfuzzer discovered a use-after-free issue in the list indenting implementation. - CVE-2013-2927 cloudfuzzer discovered a use-after-free issue in the HTML form submission implementation. - CVE-2013-2923 and CVE-2013-2928 The chrome 30 development team found various issues from internal fuzzing, audits, and other studies.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 70636
    published 2013-10-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70636
    title Debian DSA-2785-1 : chromium-browser - several vulnerabilities
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_GOOGLE_CHROME_30_0_1599_66.NASL
    description