Google Chrome 29.0.1547.76 Popup Blocker popup_blocker_tab_helper.cc AddBlockedPopup Empty URL use after free

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.
5.9$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Chrome 29.0.1547.76. This affects the function PopupBlockerTabHelper::AddBlockedPopup of the file ui/blocked_content/popup_blocker_tab_helper.cc of the component Popup Blocker. Performing a manipulation as part of Empty URL results in use after free. This vulnerability is reported as CVE-2013-2923. Moreover, an exploit is present. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Google Chrome 29.0.1547.76 (Web Browser). This affects the function PopupBlockerTabHelper::AddBlockedPopup of the file ui/blocked_content/popup_blocker_tab_helper.cc of the component Popup Blocker. The manipulation as part of a Empty URL leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

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

The weakness was disclosed 08/17/2013 as 274020 (Website). The advisory is shared at code.google.com. This vulnerability is uniquely identified as CVE-2013-2923 since 04/11/2013. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a private exploit are known. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/13/2018). It is expected to see the exploit prices for this product increasing in the near future.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 70636 (Debian DSA-2785-1 : chromium-browser - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166720 (OpenSuSE Security Update for chromium (openSUSE-SU-2014:0065-1)).

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

The vulnerability is also documented in the databases at Tenable (70636), SecurityFocus (BID 62752†), OSVDB (97999†) and Secunia (SA55087†). Further details are available at googlechromereleases.blogspot.com. The entries VDB-9992, VDB-10161, VDB-10162 and VDB-10163 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: 6.5
VulDB Meta Temp Score: 5.9

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 70636
Nessus Name: Debian DSA-2785-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 892794
OpenVAS Name: Debian Security Advisory DSA 2785-1 (chromium-browser - several vulnerabilities
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 30.0.1599.66

Timelineinfo

04/11/2013 🔍
08/17/2013 +128 days 🔍
10/01/2013 +45 days 🔍
10/02/2013 +1 days 🔍
10/02/2013 +0 days 🔍
10/03/2013 +1 days 🔍
10/27/2013 +24 days 🔍
05/13/2018 +1659 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 274020
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-2923 (🔍)
GCVE (CVE): GCVE-0-2013-2923
GCVE (VulDB): GCVE-100-10557

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 62752
Secunia: 55087 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 97999

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 10/03/2013 14:56
Updated: 05/13/2018 10:19
Changes: 10/03/2013 14:56 (80), 05/13/2018 10:19 (8)
Complete: 🔍
Cache ID: 216:AF3: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 ▸

Interested in the pricing of exploits?

See the underground prices here!