Search Results (Refine Search)

Search Parameters:
  • Results Type: Overview
  • Keyword (text search): cpe:2.3:a:google:chrome:33.0.1750.75:*:*:*:*:*:*:*
There are 1,585 matching records.
Displaying matches 1,581 through 1,585.
Vuln ID Summary CVSS Severity
CVE-2013-6656

The XSSAuditor::init function in core/html/parser/XSSAuditor.cpp in the XSS auditor in Blink, as used in Google Chrome before 33.0.1750.117, processes POST requests by using the body of a redirecting page instead of the body of a redirect target, which allows remote attackers to obtain sensitive information via unspecified vectors.

Published: February 23, 2014; 11:48:10 PM -0500
V3.x:(not available)
V2.0: 5.0 MEDIUM
CVE-2013-6655

Use-after-free vulnerability in Blink, as used in Google Chrome before 33.0.1750.117, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to improper handling of overflowchanged DOM events during interaction between JavaScript and layout.

Published: February 23, 2014; 11:48:09 PM -0500
V3.x:(not available)
V2.0: 7.5 HIGH
CVE-2013-6654

The SVGAnimateElement::calculateAnimatedValue function in core/svg/SVGAnimateElement.cpp in Blink, as used in Google Chrome before 33.0.1750.117, does not properly handle unexpected data types, which allows remote attackers to cause a denial of service (incorrect cast) or possibly have unspecified other impact via unknown vectors.

Published: February 23, 2014; 11:48:09 PM -0500
V3.x:(not available)
V2.0: 7.5 HIGH
CVE-2013-6653

Use-after-free vulnerability in the web contents implementation in Google Chrome before 33.0.1750.117 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving attempted conflicting access to the color chooser.

Published: February 23, 2014; 11:48:09 PM -0500
V3.x:(not available)
V2.0: 7.5 HIGH
CVE-2013-6652

Directory traversal vulnerability in sandbox/win/src/named_pipe_dispatcher.cc in Google Chrome before 33.0.1750.117 on Windows allows attackers to bypass intended named-pipe policy restrictions in the sandbox via vectors related to (1) lack of checks for .. (dot dot) sequences or (2) lack of use of the \\?\ protection mechanism.

Published: February 23, 2014; 11:48:09 PM -0500
V3.x:(not available)
V2.0: 7.5 HIGH