IBM Sterling Connect:Direct for UNIX 4.2.0/4.3.0/6.0.0/6.1.0 CD UNIX stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in IBM Sterling Connect:Direct for UNIX 4.2.0/4.3.0/6.0.0/6.1.0 and classified as critical. This issue affects some unknown processing of the component CD UNIX Handler. This manipulation causes stack-based overflow. The identification of this vulnerability is CVE-2020-4587. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as critical was found in IBM Sterling Connect:Direct for UNIX 4.2.0/4.3.0/6.0.0/6.1.0 (Business Process Management Software). Affected by this vulnerability is an unknown part of the component CD UNIX Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
IBM Sterling Connect:Direct for UNIX 4.2.0, 4.3.0, 6.0.0, and 6.1.0 is vulnerable to a stack based buffer ovreflow, caused by improper bounds checking. A local attacker could manipulate CD UNIX to obtain root provileges. IBM X-Force ID: 184578.
The weakness was shared 08/24/2020 (Website). It is possible to read the advisory at ibm.com. This vulnerability is known as CVE-2020-4587 since 12/30/2019. Attacking locally is a requirement. A single authentication is necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/25/2020). It is expected to see the exploit prices for this product increasing in the near future.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.4
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: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
12/30/2019 🔍08/24/2020 🔍
08/25/2020 🔍
11/11/2020 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-4587 (🔍)
GCVE (CVE): GCVE-0-2020-4587
GCVE (VulDB): GCVE-100-160219
X-Force: 184578
Entry
Created: 08/25/2020 06:50Updated: 11/11/2020 08:17
Changes: 08/25/2020 06:50 (38), 08/25/2020 06:55 (12), 11/11/2020 08:11 (2), 11/11/2020 08:17 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.