Google Chrome 22.0.1229.79 Pepper Plugin memory corruption

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

Summaryinfo

A vulnerability marked as problematic has been reported in Google Chrome 22.0.1229.79. The affected element is an unknown function of the component Pepper Plugin. This manipulation causes memory corruption. This vulnerability is handled as CVE-2012-5111. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Google Chrome 22.0.1229.79 (Web Browser). Affected by this vulnerability is an unknown code of the component Pepper Plugin. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Google Chrome before 22.0.1229.92 does not monitor for crashes of Pepper plug-ins, which has unspecified impact and remote attack vectors.

The weakness was released 10/08/2012 by Chris Evans (Inferno) with Google Chrome Security Team as 151895 as confirmed advisory (Website). The advisory is shared at code.google.com. The public release was coordinated with Google. This vulnerability is known as CVE-2012-5111 since 09/24/2012. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/18/2021). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 62457 (FreeBSD : chromium -- multiple vulnerabilities (e6161b65-1187-11e2-afe3-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks.

Upgrading to version 22.0.1229.92 eliminates this vulnerability. The upgrade is hosted for download at googlechromereleases.blogspot.dk. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (79067), Tenable (62457), SecurityFocus (BID 55830†), OSVDB (86121†) and Secunia (SA50872†). Entries connected to this vulnerability are available at VDB-6659, VDB-6660, VDB-6662 and VDB-62636. 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.6
VulDB Meta Temp Score: 5.4

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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: 62457
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (e6161b65-1187-11e2-afe3-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: Chrome 22.0.1229.92

Timelineinfo

09/24/2012 🔍
10/08/2012 +14 days 🔍
10/08/2012 +0 days 🔍
10/08/2012 +0 days 🔍
10/08/2012 +0 days 🔍
10/08/2012 +0 days 🔍
10/09/2012 +1 days 🔍
10/10/2012 +1 days 🔍
10/12/2012 +2 days 🔍
10/14/2012 +2 days 🔍
04/18/2021 +3108 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 151895
Researcher: Chris Evans (Inferno)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2012-5111 (🔍)
GCVE (CVE): GCVE-0-2012-5111
GCVE (VulDB): GCVE-100-6661

OVAL: 🔍

X-Force: 79067
SecurityFocus: 55830 - Google Chrome Prior to 22.0.1229.92 Multiple Security Vulnerabilities
Secunia: 50872 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 86121
SecurityTracker: 1027617 - Google Chrome Multiple Flaws Let Remote Users Execute Arbitrary Code
Vulnerability Center: 36523 - Google Chrome \x3C22.0.1229.92 Remote Denial of Service and Other Unspecified Impacts, Medium

See also: 🔍

Entryinfo

Created: 10/12/2012 14:58
Updated: 04/18/2021 09:09
Changes: 10/12/2012 14:58 (81), 04/19/2017 10:30 (11), 04/18/2021 09:09 (2)
Complete: 🔍
Committer:
Cache ID: 216:2CF: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!