Google Chrome up to 27.0.1453.116 Renderer Process information disclosure

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

Summaryinfo

A vulnerability, which was classified as problematic, was found in Google Chrome up to 27.0.1453.116. This vulnerability affects unknown code of the component Renderer Process Handler. Such manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2013-2879. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Chrome up to 27.0.1453.116 (Web Browser). Affected by this issue is some unknown functionality of the component Renderer Process Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality, and integrity. CVE summarizes:

Google Chrome before 28.0.1500.71 does not properly determine the circumstances in which a renderer process can be considered a trusted process for sign-in and subsequent sync operations, which makes it easier for remote attackers to conduct phishing attacks via a crafted web site.

The weakness was disclosed 07/09/2013 by Andrey Labunets (danguafer) with Google Security Team as not defined changelog entry (Website). The advisory is shared for download at googlechromereleases.blogspot.dk. The public release has been coordinated in cooperation with the vendor. This vulnerability is handled as CVE-2013-2879 since 04/11/2013. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

The vulnerability scanner Nessus provides a plugin with the ID 68970 (Debian DSA-2724-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. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121317 (Google Chrome Prior to 28.0.1500.71 Multiple Vulnerabilities).

Upgrading to version 28.0.1500.71 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 (85528), Tenable (68970), SecurityFocus (BID 61041†), OSVDB (95021†) and Secunia (SA54017†). The entries VDB-8662, VDB-8869, VDB-8995 and VDB-9451 are pretty similar. Once again VulDB remains the best source for vulnerability data.

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: 6.2

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
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: 68970
Nessus Name: Debian DSA-2724-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 892724
OpenVAS Name: Debian Security Advisory DSA 2724-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 28.0.1500.71

Timelineinfo

04/11/2013 🔍
07/09/2013 +89 days 🔍
07/09/2013 +0 days 🔍
07/09/2013 +0 days 🔍
07/09/2013 +0 days 🔍
07/09/2013 +0 days 🔍
07/10/2013 +1 days 🔍
07/10/2013 +0 days 🔍
07/11/2013 +1 days 🔍
05/18/2021 +2868 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.dk
Researcher: Andrey Labunets (danguafer)
Organization: Google Security Team
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2879 (🔍)
GCVE (CVE): GCVE-0-2013-2879
GCVE (VulDB): GCVE-100-9452

OVAL: 🔍
IAVM: 🔍

X-Force: 85528
SecurityFocus: 61041 - RETIRED: Google Chrome Prior to 28.0.1500.71 Multiple Security Vulnerabilities
Secunia: 54017 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 95021
Vulnerability Center: 40435 - Google Chrome <28.0.1500.71 Allows Phishing due to Improper Verification of Processes CVE-2013-2879, Medium

See also: 🔍

Entryinfo

Created: 07/11/2013 16:16
Updated: 05/18/2021 15:12
Changes: 07/11/2013 16:16 (85), 05/05/2017 08:57 (6), 05/18/2021 15:12 (3)
Complete: 🔍
Committer:
Cache ID: 216:0BC:103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!