| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in IBM DB2 9.5. Affected by this issue is some unknown functionality of the component nodes.reg. This manipulation causes access control. This vulnerability is registered as CVE-2012-1797. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in IBM DB2 9.5 (Database Software). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component nodes.reg. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors.
The weakness was published 02/15/2012 (Website). The advisory is shared at www-01.ibm.com. This vulnerability is known as CVE-2012-1797 since 03/20/2012. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 802727 , which helps to determine the existence of the flaw in a target environment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 120294 (IBM DB2 Multiple Vulnerabilities).
Applying a patch is able to eliminate this problem. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (74326), Tenable (802727), OSVDB (80343†) and Vulnerability Center (SBV-35412†). Similar entries are available at VDB-4715, VDB-4716, VDB-4717 and VDB-4718. 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: 9.1VulDB Meta Temp Score: 7.9
VulDB Base Score: 9.1
VulDB Temp Score: 7.9
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 802727
Nessus File: 🔍
Nessus Risk: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
10/28/2011 🔍02/15/2012 🔍
03/20/2012 🔍
03/20/2012 🔍
03/20/2012 🔍
03/23/2012 🔍
03/25/2012 🔍
04/03/2012 🔍
06/24/2012 🔍
04/14/2017 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2012-1797 (🔍)
GCVE (CVE): GCVE-0-2012-1797
GCVE (VulDB): GCVE-100-4885
OVAL: 🔍
IAVM: 🔍
X-Force: 74326 - IBM DB2 nodes.reg unspecified, Medium Risk
OSVDB: 80343
Vulnerability Center: 35412 - IBM DB2 9.5 nodes.reg World-Writeable Permissions Causes Unknown Impact, Medium
See also: 🔍
Entry
Created: 03/25/2012 20:32Updated: 04/14/2017 10:12
Changes: 03/25/2012 20:32 (68), 04/14/2017 10:12 (6)
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.