Google Chrome 23.0.1271.97 Geolocations 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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Chrome 23.0.1271.97. The impacted element is an unknown function of the component Geolocations Handler. This manipulation causes denial of service. This vulnerability appears as CVE-2013-0835. In addition, an exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 23.0.1271.97 (Web Browser). It has been declared as critical. Affected by this vulnerability is an unknown code of the component Geolocations Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:

Unspecified vulnerability in the Geolocation implementation in Google Chrome before 24.0.1312.52 allows remote attackers to cause a denial of service (application crash) via unknown vectors.

The weakness was presented 01/10/2013 by Arthur Gerkis (Inferno) with Chromium Development Community as 152921 as confirmed advisory (Website). The advisory is shared at code.google.com. The public release was coordinated in cooperation with Google. This vulnerability is known as CVE-2013-0835 since 01/07/2013. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 63469 (FreeBSD : chromium -- multiple vulnerabilities (46bd747b-5b84-11e2-b06d-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 166158 (SUSE Security Update for Chromium (openSUSE-SU-2013:0236-1)).

Upgrading to version 24.0.1312.52 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 (81142), Tenable (63469), SecurityFocus (BID 57251†), OSVDB (89091†) and Secunia (SA51825†). See VDB-7314, VDB-7315, VDB-7316 and VDB-7317 for similar entries. 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.9
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.9
VulDB Temp Score: 5.3
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: 63469
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (46bd747b-5b84-11e2-b06d-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 803158
OpenVAS Name: Google Chrome Multiple Vulnerabilities-01 Jan2013 (Linux)
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 24.0.1312.52

Timelineinfo

01/07/2013 🔍
01/10/2013 +3 days 🔍
01/10/2013 +0 days 🔍
01/10/2013 +0 days 🔍
01/10/2013 +0 days 🔍
01/11/2013 +1 days 🔍
01/12/2013 +1 days 🔍
01/15/2013 +3 days 🔍
01/15/2013 +0 days 🔍
01/21/2013 +6 days 🔍
04/22/2021 +3013 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 152921
Researcher: Arthur Gerkis (Inferno)
Organization: Chromium Development Community
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-0835 (🔍)
GCVE (CVE): GCVE-0-2013-0835
GCVE (VulDB): GCVE-100-7333

OVAL: 🔍

X-Force: 81142
SecurityFocus: 57251 - RETIRED: Google Chrome Prior to 24.0.1312.52 Multiple Security Vulnerabilities
Secunia: 51825 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 89091
SecurityTracker: 1027977 - Google Chrome Multiple Flaws Let Remote Users Execute Arbitrary Code
Vulnerability Center: 38131 - Google Chrome Before 24.0.1312.52 Geolocation Implementation Unspecified Remote DoS Vulnerability, Medium

See also: 🔍

Entryinfo

Created: 01/15/2013 14:57
Updated: 04/22/2021 08:18
Changes: 01/15/2013 14:57 (88), 04/24/2017 09:40 (5), 04/22/2021 08:18 (3)
Complete: 🔍
Committer:
Cache ID: 216:5A2: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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!