Parity Browser up to 1.6.10 Web Proxy Engine Request 7pk security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Parity Browser up to 1.6.10. Affected by this issue is some unknown functionality of the component Web Proxy Engine. Executing a manipulation as part of Request can lead to 7pk security. This vulnerability is tracked as CVE-2017-18016. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability classified as critical was found in Parity Browser up to 1.6.10. This vulnerability affects an unknown part of the component Web Proxy Engine. The manipulation as part of a Request leads to a 7pk security vulnerability. The CWE definition for the vulnerability is CWE-254. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Parity Browser 1.6.10 and earlier allows remote attackers to bypass the Same Origin Policy and obtain sensitive information by requesting other websites via the Parity web proxy engine (reusing the current website's token, which is not bound to an origin).
The bug was discovered 01/10/2018. The weakness was disclosed 01/11/2018 (oss-sec). The advisory is shared for download at openwall.com. This vulnerability was named CVE-2017-18016 since 01/02/2018. The attack can be initiated remotely. A single authentication is necessary for exploitation. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1211.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (43499). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.5
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: 7pk securityCWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
01/02/2018 🔍01/10/2018 🔍
01/11/2018 🔍
01/11/2018 🔍
01/12/2018 🔍
06/22/2025 🔍
Sources
Advisory: 53609f703e2f1af76441344ac3b72811c726a215Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-18016 (🔍)
GCVE (CVE): GCVE-0-2017-18016
GCVE (VulDB): GCVE-100-111772
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/12/2018 08:05Updated: 06/22/2025 11:54
Changes: 01/12/2018 08:05 (45), 12/22/2019 15:17 (10), 01/29/2021 21:34 (12), 01/20/2023 15:41 (4), 06/22/2025 11:54 (19)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.