| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in IBM DB2 9.7/10.1/10.5/11.1/11.5. Affected by this issue is some unknown functionality. The manipulation leads to race condition. This vulnerability is referenced as CVE-2020-4386. The attack can only be performed from a local environment. No exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in IBM DB2 9.7/10.1/10.5/11.1/11.5 (Database Software). This issue affects some unknown functionality. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality. The summary by CVE is:
IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, 11.1, and 11.5 could allow a local user to obtain sensitive information using a race condition of a symbolic link. IBM X-Force ID: 179268.
The weakness was published 07/01/2020 (Website). The advisory is shared at ibm.com. The identification of this vulnerability is CVE-2020-4386 since 12/30/2019. An attack has to be approached locally. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-157568, VDB-157567, VDB-157566 and VDB-157563. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.2
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: Race conditionCWE: CWE-362
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 🔍07/01/2020 🔍
07/02/2020 🔍
10/28/2020 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-4386 (🔍)
GCVE (CVE): GCVE-0-2020-4386
GCVE (VulDB): GCVE-100-157565
X-Force: 179268
See also: 🔍
Entry
Created: 07/02/2020 15:48Updated: 10/28/2020 12:40
Changes: 07/02/2020 15:48 (37), 07/02/2020 15:53 (12), 10/28/2020 12:31 (2), 10/28/2020 12:40 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.