ibm_db up to 1.0.1 on Node.js Download cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in ibm_db up to 1.0.1 on Node.js. Affected by this vulnerability is an unknown functionality of the component Download Handler. Such manipulation leads to cryptographic issue. This vulnerability is documented as CVE-2016-10577. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in ibm_db up to 1.0.1 on Node.js (JavaScript Library). Affected by this issue is some unknown functionality of the component Download Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality, integrity, and availability. CVE summarizes:
ibm_db is an asynchronous/synchronous interface for node.js to IBM DB2 and IBM Informix. ibm_db before 1.0.2 downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
The bug was discovered 12/18/2016. The weakness was released 05/29/2018 (Website). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2016-10577 since 10/29/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.
The vulnerability was handled as a non-public zero-day exploit for at least 527 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.0.2 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
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: Cryptographic issueCWE: CWE-310
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: ibm_db 1.0.2
Patch: github.com
Timeline
12/18/2016 🔍10/29/2017 🔍
05/29/2018 🔍
05/29/2018 🔍
05/30/2018 🔍
03/17/2023 🔍
Sources
Advisory: d7e2d4b4cbeb6f067df8bba7d0b2ac5d40fcfc19Status: Not defined
CVE: CVE-2016-10577 (🔍)
GCVE (CVE): GCVE-0-2016-10577
GCVE (VulDB): GCVE-100-118316
Entry
Created: 05/30/2018 08:52Updated: 03/17/2023 15:05
Changes: 05/30/2018 08:52 (60), 02/09/2020 15:40 (1), 03/17/2023 15:05 (5)
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.