| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in IBM WebSphere MQ up to 7.0.1.2. The affected element is an unknown function. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2011-0314. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in IBM WebSphere MQ up to 7.0.1.2 (Application Server Software) and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Heap-based buffer overflow in IBM WebSphere MQ 6.0 before 6.0.2.11 and 7.0 before 7.0.1.5 allows remote authenticated users to execute arbitrary code or cause a denial of service (queue manager crash) by inserting an invalid message into the queue.
The weakness was shared 01/11/2011 (Website). The advisory is shared at xforce.iss.net. This vulnerability is known as CVE-2011-0314. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. Neither technical details nor an exploit are publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 86960 (IBM WebSphere MQ Message Buffer Overflow Vulnerability (IZ81294)).
Upgrading to version 7.0.1.3 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (64550), SecurityFocus (BID 45801†) and Vulnerability Center (SBV-33475†). 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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WebSphere MQ 7.0.1.3
Timeline
01/06/2011 🔍01/11/2011 🔍
01/11/2011 🔍
01/11/2011 🔍
01/13/2011 🔍
10/09/2011 🔍
03/19/2015 🔍
01/19/2025 🔍
Sources
Vendor: ibm.comAdvisory: xforce.iss.net
Status: Confirmed
CVE: CVE-2011-0314 (🔍)
GCVE (CVE): GCVE-0-2011-0314
GCVE (VulDB): GCVE-100-56029
X-Force: 64550
SecurityFocus: 45801 - IBM WebSphere MQ Invalid Message Remote Buffer Overflow Vulnerability
Secunia: 42941
Vulnerability Center: 33475 - IBM WebSphere MQ before 6.0.2.11 and 7.0.1.5 Buffer Overflow Allows Privilege Escalation, Medium
Entry
Created: 03/19/2015 23:27Updated: 01/19/2025 07:04
Changes: 03/19/2015 23:27 (49), 04/03/2017 17:48 (9), 10/11/2021 14:58 (4), 01/19/2025 07:04 (18)
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.