| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in IBM i Access 7.1 and classified as problematic. This impacts an unknown function of the component Privileges. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2014-8920. No exploit exists.
Details
A vulnerability was found in IBM i Access 7.1. It has been classified as critical. This affects an unknown part of the component Privileges. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in the Data Transfer Program in IBM i Access 5770-XE1 5R4, 6.1, and 7.1 on Windows allows local users to gain privileges via unspecified vectors.
The weakness was disclosed 01/28/2015 (Website). The advisory is shared at www-01.ibm.com. This vulnerability is uniquely identified as CVE-2014-8920 since 11/14/2014. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. 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 06/19/2017). 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 vulnerability is also documented in the databases at X-Force (99311), SecurityFocus (BID 72314†), Secunia (SA62532†) and Vulnerability Center (SBV-48508†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 9.3VulDB Meta Temp Score: 9.3
VulDB Base Score: 9.3
VulDB Temp Score: 9.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 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
11/14/2014 🔍01/19/2015 🔍
01/19/2015 🔍
01/26/2015 🔍
01/28/2015 🔍
01/28/2015 🔍
02/08/2015 🔍
03/27/2015 🔍
06/19/2017 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-8920 (🔍)
GCVE (CVE): GCVE-0-2014-8920
GCVE (VulDB): GCVE-100-73797
X-Force: 99311
SecurityFocus: 72314 - IBM i Access for Windows CVE-2014-8920 Local Buffer Overflow Vulnerability
Secunia: 62532 - IBM i Access for Windows Buffer Overflow Privilege Escalation Vulnerability, Less Critical
Vulnerability Center: 48508 - IBM i Access for Windows Local Buffer Overflow and Code Execution, Medium
Entry
Created: 03/27/2015 14:56Updated: 06/19/2017 08:39
Changes: 03/27/2015 14:56 (56), 06/19/2017 08:39 (7)
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.