Yandex Browser up to 17.4.0 on Android HTML Page race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Yandex Browser up to 17.4.0 on Android. It has been declared as critical. This vulnerability affects unknown code. Executing a manipulation as part of HTML Page can lead to race condition. This vulnerability appears as CVE-2017-7326. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in Yandex Browser up to 17.4.0 on Android (Android App Software). This vulnerability affects some unknown processing. The manipulation as part of a HTML Page 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. CVE summarizes:
Race condition issue in Yandex Browser for Android before 17.4.0.16 allowed a remote attacker to potentially exploit memory corruption via a crafted HTML page
The bug was discovered 01/18/2017. The weakness was presented 01/19/2018 (Website). The advisory is available at browser.yandex.com. This vulnerability was named CVE-2017-7326 since 03/30/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 366 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 17.4.0.16 eliminates this vulnerability.
See VDB-112259 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: Race conditionCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Browser 17.4.0.16
Timeline
01/18/2017 🔍03/30/2017 🔍
01/19/2018 🔍
01/19/2018 🔍
01/20/2018 🔍
12/25/2019 🔍
Sources
Advisory: browser.yandex.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-7326 (🔍)
GCVE (CVE): GCVE-0-2017-7326
GCVE (VulDB): GCVE-100-112258
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 01/20/2018 13:32Updated: 12/25/2019 13:41
Changes: 01/20/2018 13:32 (61), 12/25/2019 13:41 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.