Yahoo! Browser 1.2.0/1.4.2 Address Bar authentication spoofing

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 described as critical has been identified in Yahoo! Browser 1.2.0/1.4.2. This vulnerability affects unknown code of the component Address Bar. Such manipulation leads to authentication spoofing. This vulnerability is traded as CVE-2013-2307. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Yahoo! Browser 1.2.0/1.4.2. It has been rated as critical. Affected by this issue is an unknown code block of the component Address Bar. The manipulation with an unknown input leads to a authentication spoofing vulnerability. Using CWE to declare the problem leads to CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. Impacted is confidentiality, and integrity. CVE summarizes:

The Yahoo! Browser application before 1.4.3 for Android allows remote attackers to spoof the address bar via a crafted web site.

The weakness was shared 04/26/2013 (Website). The advisory is available at play.google.com. This vulnerability is handled as CVE-2013-2307 since 03/04/2013. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.

Upgrading to version 1.2.0 eliminates this vulnerability.

The entry VDB-61308 is related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

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: Authentication spoofing
CWE: CWE-290 / CWE-287
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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Browser 1.2.0

Timelineinfo

03/04/2013 🔍
04/26/2013 +53 days 🔍
04/26/2013 +0 days 🔍
03/24/2015 +697 days 🔍
02/26/2019 +1435 days 🔍

Sourcesinfo

Vendor: yahoo.com

Advisory: play.google.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2013-2307 (🔍)
GCVE (CVE): GCVE-0-2013-2307
GCVE (VulDB): GCVE-100-64034
See also: 🔍

Entryinfo

Created: 03/24/2015 15:54
Updated: 02/26/2019 09:07
Changes: 03/24/2015 15:54 (48), 02/26/2019 09:07 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit 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!