Google Chrome 23.0.1271.91 denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Google Chrome 23.0.1271.91. This affects an unknown function. The manipulation leads to denial of service. This vulnerability is uniquely identified as CVE-2012-5132. Moreover, an exploit is present. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 23.0.1271.91 (Web Browser). It has been rated as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:

Google Chrome before 23.0.1271.91 allows remote attackers to cause a denial of service (application crash) via a response with chunked transfer coding.

The weakness was disclosed 11/26/2012 by Atte Kettunen (Inferno) with Google Chrome Security Team as 155711 (Website). The advisory is shared at code.google.com. The public release has been coordinated in cooperation with Google. The identification of this vulnerability is CVE-2012-5132 since 09/24/2012. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.

It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 63069 (FreeBSD : chromium -- multiple vulnerabilities (4d64fc61-3878-11e2-a4eb-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 120697 (Google Chrome Prior to 23.0.1271.91 Multiple Vulnerabilities).

Upgrading to version 23.0.1271.91, eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (80293), Tenable (63069), SecurityFocus (BID 56684†), OSVDB (87887†) and Secunia (SA51437†). The entries VDB-7032, VDB-7033, VDB-7034 and VDB-7035 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 6.5

VulDB Base Score: 7.5
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 63069
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (4d64fc61-3878-11e2-a4eb-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 850379
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2012:1637-1 (Chromium)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 23.0.1271.91,

Timelineinfo

09/24/2012 🔍
11/26/2012 +63 days 🔍
11/26/2012 +0 days 🔍
11/26/2012 +0 days 🔍
11/27/2012 +1 days 🔍
11/27/2012 +0 days 🔍
11/27/2012 +0 days 🔍
11/27/2012 +0 days 🔍
11/30/2012 +3 days 🔍
12/19/2012 +19 days 🔍
04/19/2021 +3043 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 155711
Researcher: Atte Kettunen (Inferno)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5132 (🔍)
GCVE (CVE): GCVE-0-2012-5132
GCVE (VulDB): GCVE-100-7037

OVAL: 🔍

X-Force: 80293 - Google Chrome chunked encoding denial of service, Medium Risk
SecurityFocus: 56684
Secunia: 51437 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 87887
SecurityTracker: 1027815 - Google Chrome Multiple Flaws Let Remote Users Execute Arbitrary Code
Vulnerability Center: 37722 - Google Chrome Before 23.0.1271.91 Remote DoS Vulnerability via a Chunked Transfer Coding, Medium

See also: 🔍

Entryinfo

Created: 11/30/2012 10:35
Updated: 04/19/2021 16:09
Changes: 11/30/2012 10:35 (89), 04/22/2017 17:18 (3), 04/19/2021 16:09 (3)
Complete: 🔍
Committer:
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!