Apple iTunes 10.6.3 WebKit race condition

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

Summaryinfo

A vulnerability marked as problematic has been reported in Apple iTunes 10.6.3. This affects an unknown function of the component WebKit. This manipulation causes race condition. This vulnerability is tracked as CVE-2011-3090. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Apple iTunes 10.6.3 (Multimedia Player Software). Affected by this vulnerability is an unknown code of the component WebKit. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Race condition in Google Chrome before 19.0.1084.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to worker processes.

The weakness was disclosed 09/12/2012 by Arthur Gerkis (psaldorn) with Chromium Development Community as APPLE-SA-2012-09-12-1 as confirmed posting (Website). The advisory is shared at lists.apple.com. The public release has been coordinated in cooperation with Apple. This vulnerability is known as CVE-2011-3090 since 08/09/2011. The exploitation appears to be easy. 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 vulnerability scanner Nessus provides a plugin with the ID 59103 (FreeBSD : chromium -- multiple vulnerabilities (1449af37-9eba-11e1-b9c1-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165306 (SUSE Security Update for Update for Chromium, v8 (openSUSE-SU-2012:0656-1)).

Upgrading to version 10.7 eliminates this vulnerability. The upgrade is hosted for download at apple.com. The problem might be mitigated by replacing the product with Spotify as an alternative. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (59103), SecurityFocus (BID 53540†) and SecurityTracker (ID 1027067†). The entries VDB-4607, VDB-4576, VDB-4572 and VDB-4615 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: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
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: 59103
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (1449af37-9eba-11e1-b9c1-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 71375
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: iTunes 10.7
Alternative: Spotify

Timelineinfo

08/09/2011 🔍
05/15/2012 +280 days 🔍
05/15/2012 +0 days 🔍
05/15/2012 +0 days 🔍
05/16/2012 +1 days 🔍
05/16/2012 +0 days 🔍
09/12/2012 +119 days 🔍
09/13/2012 +0 days 🔍
04/12/2021 +3133 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: APPLE-SA-2012-09-12-1
Researcher: Arthur Gerkis (psaldorn)
Organization: Chromium Development Community
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2011-3090 (🔍)
GCVE (CVE): GCVE-0-2011-3090
GCVE (VulDB): GCVE-100-6157

OVAL: 🔍

X-Force: 75595
SecurityFocus: 53540 - Google Chrome Prior to 19 Multiple Security Vulnerabilities
SecurityTracker: 1027067

See also: 🔍

Entryinfo

Created: 09/13/2012 11:44
Updated: 04/12/2021 10:46
Changes: 09/13/2012 11:44 (77), 04/29/2018 10:48 (7), 04/12/2021 10:46 (3)
Complete: 🔍
Cache ID: 216:EFD: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 know our Splunk app?

Download it now for free!