Menu

Star on GitHub · 3.2k

CVE-2013-6667

7.5 · HIGH

Multiple unspecified vulnerabilities in Google Chrome before 33.0.1750.146 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Published Mar 5, 2014googleEPSS 1.38%

Overview

CVE-2013-6667 is a high-severity vulnerability affecting google chrome. It was published on March 5, 2014 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Multiple unspecified vulnerabilities in Google Chrome before 33.0.1750.146 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

Remediation

Check the references section for vendor advisories and patches from google. Update chrome to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
googlechrome0Affected

Frequently asked questions

What is CVE-2013-6667?

CVE-2013-6667 is a high-severity vulnerability affecting google chrome. It was published on March 5, 2014 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2013-6667?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2013-6667?

Check the references section for vendor advisories and patches from google. Update chrome to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2013-6667?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2013-6667 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2013

View all