Google Chrome up to 13.0.782.x Installation input validation

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.2$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome up to 13.0.782.x. Affected by this vulnerability is an unknown functionality of the component Installation. The manipulation leads to input validation. This vulnerability is uniquely identified as CVE-2011-2783. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 13.0.782.x (Web Browser). It has been rated as problematic. This issue affects an unknown functionality of the component Installation. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is integrity, and availability. The summary by CVE is:

Google Chrome before 13.0.782.107 does not ensure that developer-mode NPAPI extension installations are confirmed by a browser dialog, which makes it easier for remote attackers to modify the product s functionality via a Trojan horse extension.

The weakness was disclosed 08/02/2011 by Sergey Glazunov (miaubiz) with Chromium Development Community (Website). The advisory is shared at xforce.iss.net. The identification of this vulnerability is CVE-2011-2783. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 51069 (FreeBSD : chromium -- multiple vulnerabilities (6887828f-0229-11e0-b84d-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 119485 (Google Chrome Prior to 13.0.782.107 Multiple Vulnerabilities).

Upgrading to version 8.0.552.209 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 11981.

The vulnerability is also documented in the databases at X-Force (68945), Tenable (51069), SecurityFocus (BID 48960†), OSVDB (74233†) and Vulnerability Center (SBV-32615†). The entries VDB-4341, VDB-4385, VDB-56943 and VDB-56942 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: 5.4
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 51069
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (6887828f-0229-11e0-b84d-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 68696
OpenVAS Name: FreeBSD Ports: chromium
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 8.0.552.209
TippingPoint: 🔍

Timelineinfo

07/20/2011 🔍
08/02/2011 +13 days 🔍
08/02/2011 +0 days 🔍
08/02/2011 +0 days 🔍
08/02/2011 +0 days 🔍
08/08/2011 +6 days 🔍
03/23/2015 +1323 days 🔍
11/15/2021 +2429 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: xforce.iss.net
Researcher: Sergey Glazunov (miaubiz)
Organization: Chromium Development Community
Status: Not defined
Confirmation: 🔍

CVE: CVE-2011-2783 (🔍)
GCVE (CVE): GCVE-0-2011-2783
GCVE (VulDB): GCVE-100-58157

OVAL: 🔍

X-Force: 68945
SecurityFocus: 48960 - Google Chrome Prior to 13.0.782.107 Multiple Security Vulnerabilities
OSVDB: 74233
Vulnerability Center: 32615 - Google Chrome prior to 13.0.782.107 Allows to Modify the Product\x27s Functionality, Medium

See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 11/15/2021 23:28
Changes: 03/23/2015 16:50 (66), 03/29/2017 11:05 (12), 11/15/2021 23:16 (4), 11/15/2021 23:28 (1)
Complete: 🔍
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!