| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Ingres 2.6/2006. This vulnerability affects unknown code. The manipulation leads to access control. This vulnerability is documented as CVE-2008-3356. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Ingres 2.6/2006. It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
verifydb in Ingres 2.6, Ingres 2006 release 1 (aka 9.0.4), and Ingres 2006 release 2 (aka 9.1.0) on Linux and other Unix platforms sets the ownership or permissions of an iivdb.log file without verifying that it is the application s own log file, which allows local users to overwrite arbitrary files by creating a symlink with an iivdb.log filename.
The weakness was released 08/05/2008 with iDEFENSE (Website). The advisory is shared at support.ca.com. The identification of this vulnerability is CVE-2008-3356 since 07/28/2008. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as highly functional.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (44177), SecurityFocus (BID 30512†), Secunia (SA31357†) and SecurityTracker (ID 1020613†). Entries connected to this vulnerability are available at VDB-43543 and VDB-43542. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
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: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Highly functional
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
07/28/2008 🔍08/01/2008 🔍
08/03/2008 🔍
08/05/2008 🔍
08/05/2008 🔍
03/17/2015 🔍
03/17/2015 🔍
Sources
Advisory: support.ca.comOrganization: iDEFENSE
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-3356 (🔍)
GCVE (CVE): GCVE-0-2008-3356
GCVE (VulDB): GCVE-100-43541
X-Force: 44177 - Ingres Database verifydb symlink
SecurityFocus: 30512 - Ingres Database Multiple Local Vulnerabilities
Secunia: 31357
SecurityTracker: 1020613
Vupen: ADV-2008-2292
See also: 🔍
Entry
Created: 03/17/2015 12:19Changes: 03/17/2015 12:19 (61)
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.