Google V8 vulnerabilities

In Google V8 before version 5.0.71.32, used in Google Chrome before version 51.0.2704.63, there is an issue with improper restriction of lazy deoptimization. This may allow remote attackers to cause a denial of service (heap-based buffer overflow) or potentially have unspecified other impact via crafted JavaScript code.

Multiple unspecified vulnerabilities in Google V8 before version 4.9.385.33, as used in Google Chrome before version 49.0.2623.108, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Multiple unspecified vulnerabilities in Google V8 before version 4.7.80.23, as used in Google Chrome before version 47.0.2526.80, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Multiple unspecified vulnerabilities in Google V8 before version 4.7.80.23, as used in Google Chrome before version 47.0.2526.73, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Multiple unspecified vulnerabilities in Google V8 before version 4.6.85.23, as used in Google Chrome before version 46.0.2490.71, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Multiple unspecified vulnerabilities in Google V8 before version 4.5.103.29, as used in Google Chrome before version 45.0.2454.85, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The factory.cc file in Google V8, used in Google Chrome before version 40.0.2214.91, contains a vulnerability that allows remote attackers to cause a denial of service (memory corruption) or potentially unspecified other impact via crafted JavaScript code that triggers improper maintenance of backing-store pointers.

Multiple unspecified vulnerabilities in Google V8 before version 3.24.35.33, as used in Google Chrome before version 34.0.1847.131 on Windows and OS X and before version 34.0.1847.132 on Linux, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Google V8, used in Google Chrome before version 34.0.1847.131 on Windows and OS X and before 34.0.1847.132 on Linux, improperly stores internationalization metadata. This allows remote attackers to bypass intended access restrictions by leveraging 'type confusion' and reading property values.

Google V8, used in Google Chrome before version 34.0.1847.116, does not properly implement lazy deoptimization, allowing remote attackers to cause a denial of service (memory corruption) or possibly other unspecified impacts via crafted JavaScript code.

Google V8, used in Google Chrome before version 34.0.1847.116, improperly performs numeric casts during typed array handling. This allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted JavaScript code.

Google V8, as used in Google Chrome before version 33.0.1750.152 on OS X and Linux and before version 33.0.1750.154 on Windows, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.

Multiple unspecified vulnerabilities in Google V8 before version 4.8.271.17, as used in Google Chrome before version 48.0.2564.82, may allow attackers to cause a denial of service or possibly have other impact via unknown vectors.