Google Chrome OS up to 25.0.1364.173 Google Talk Plugin access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Chrome OS up to 25.0.1364.173. This issue affects some unknown processing of the component Google Talk Plugin. The manipulation leads to access control. This vulnerability is documented as CVE-2013-2834. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Google Chrome OS up to 25.0.1364.173 (Web Browser). It has been rated as critical. This issue affects some unknown processing of the component Google Talk Plugin. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is integrity. The summary by CVE is:
Google Chrome OS before 26.0.1410.57 does not properly enforce origin restrictions for the O3D and Google Talk plug-ins, which allows remote attackers to bypass the domain-whitelist protection mechanism via a crafted web site, a different vulnerability than CVE-2013-2835.
The weakness was released 04/15/2013 by Chris Evans with Google Chrome Security Team as not defined bulletin (Website). The advisory is shared at googlechromereleases.blogspot.ch. The public release was coordinated with Google. The identification of this vulnerability is CVE-2013-2834 since 04/11/2013. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/05/2018). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 26.0.1410.57 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.chromium.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (92495†). Entries connected to this vulnerability are available at VDB-8442, VDB-8443 and VDB-8444. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome OS 26.0.1410.57
Patch: git.chromium.org
Timeline
04/11/2013 🔍04/15/2013 🔍
04/15/2013 🔍
04/16/2013 🔍
04/19/2013 🔍
05/05/2018 🔍
Sources
Vendor: google.comAdvisory: googlechromereleases.blogspot.ch
Researcher: Chris Evans
Organization: Google Chrome Security Team
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2013-2834 (🔍)
GCVE (CVE): GCVE-0-2013-2834
GCVE (VulDB): GCVE-100-8441
OSVDB: 92495
See also: 🔍
Entry
Created: 04/19/2013 17:58Updated: 05/05/2018 18:06
Changes: 04/19/2013 17:58 (56), 05/05/2018 18:06 (6)
Complete: 🔍
Committer:
Cache ID: 216:586:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.