Bitpay Insight-api up to 5.0.0 Web Request Path input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Bitpay Insight-api up to 5.0.0. It has been classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation as part of Web Request leads to input validation (Path). This vulnerability is traded as CVE-2018-1000023. It is possible to initiate the attack remotely. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as problematic, has been found in Bitpay Insight-api up to 5.0.0 (Automation Software). This issue affects an unknown code block. The manipulation as part of a Web Request leads to a input validation vulnerability (Path). Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality. The summary by CVE is:
Bitpay/insight-api Insight-api version 5.0.0 and earlier contains a CWE-20: input validation vulnerability in transaction broadcast endpoint that can result in Full Path Disclosure. This attack appear to be exploitable via Web request.
The bug was discovered 01/11/2018. The weakness was shared 02/09/2018 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-1000023 since 01/29/2018. The exploitation is known to be easy. 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 vulnerability was handled as a non-public zero-day exploit for at least 29 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
Website
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: 4.9
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
Name: PathClass: Input validation / Path
CWE: CWE-20
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/11/2018 🔍01/29/2018 🔍
02/09/2018 🔍
02/09/2018 🔍
02/10/2018 🔍
02/06/2023 🔍
Sources
Product: github.comAdvisory: 542
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-1000023 (🔍)
GCVE (CVE): GCVE-0-2018-1000023
GCVE (VulDB): GCVE-100-113069
Entry
Created: 02/10/2018 09:19 AMUpdated: 02/06/2023 09:51 AM
Changes: 02/10/2018 09:19 AM (58), 01/03/2020 02:05 PM (2), 02/06/2023 09:51 AM (4)
Complete: 🔍
Cache ID: 244:0A6:40
No comments yet. Languages: en.
Please log in to comment.