| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in IBM i2 Intelligent Analyis Platform 9.2.1. Affected is an unknown function. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2020-4264. Local access is required to approach this attack. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in IBM i2 Intelligent Analyis Platform 9.2.1. This issue affects some unknown functionality. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
IBM i2 Intelligent Analyis Platform 9.2.1 could allow a local attacker to execute arbitrary code on the system, caused by a memory corruption. By persuading a victim to open a specially-crafted file, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 175647.
The weakness was disclosed 05/14/2020 (Website). The advisory is shared at exchange.xforce.ibmcloud.com. The identification of this vulnerability is CVE-2020-4264 since 12/30/2019. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/15/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.
The entries VDB-155291, VDB-155292, VDB-155294 and VDB-155295 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
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: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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 🔍05/14/2020 🔍
05/15/2020 🔍
10/18/2020 🔍
Sources
Vendor: ibm.comAdvisory: exchange.xforce.ibmcloud.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-4264 (🔍)
GCVE (CVE): GCVE-0-2020-4264
GCVE (VulDB): GCVE-100-155297
X-Force: 175647
See also: 🔍
Entry
Created: 05/15/2020 09:38Updated: 10/18/2020 10:26
Changes: 05/15/2020 09:38 (39), 05/15/2020 09:43 (17), 10/18/2020 10:18 (1), 10/18/2020 10:26 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.