| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in IBM WebSphere MQ 8.0/9.0. It has been rated as problematic. The impacted element is an unknown function of the component MQXR Channel. The manipulation leads to access control. This vulnerability is referenced as CVE-2017-1117. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in IBM WebSphere MQ 8.0/9.0 (Application Server Software). It has been rated as problematic. This issue affects an unknown function of the component MQXR Channel. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is availability. The summary by CVE is:
IBM WebSphere MQ 8.0 and 9.0 could allow an authenticated user to cause a denial of service to the MQXR channel when trace is enabled. IBM X-Force ID: 121155.
The bug was discovered 06/19/2017. The weakness was published 06/21/2017 (Website). The advisory is shared at ibm.com. The identification of this vulnerability is CVE-2017-1117 since 11/30/2016. The attack may be initiated remotely. The successful exploitation requires a simple authentication. 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 12/29/2020). MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k.
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 vulnerability database at SecurityFocus (BID 99136†). 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.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Access controlCWE: CWE-284 / CWE-266
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 |
OpenVAS ID: 103277
OpenVAS Name: IBM WebSphere MQ Denial of Service Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/30/2016 🔍06/19/2017 🔍
06/19/2017 🔍
06/21/2017 🔍
06/21/2017 🔍
06/22/2017 🔍
12/29/2020 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Researcher: IBM
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1117 (🔍)
GCVE (CVE): GCVE-0-2017-1117
GCVE (VulDB): GCVE-100-102725
OVAL: 🔍
X-Force: 121155
SecurityFocus: 99136 - IBM WebSphere MQ CVE-2017-1117 Denial of Service Vulnerability
Entry
Created: 06/22/2017 08:54Updated: 12/29/2020 12:15
Changes: 06/22/2017 08:54 (64), 10/19/2019 16:10 (4), 12/29/2020 12:11 (3), 12/29/2020 12:15 (1)
Complete: 🔍
Cache ID: 216:D48: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.