CVE-2008-3357 json
Untrusted search path vulnerability in ingvalidpw in Ingres 2.6, Ingres 2006 release 1 (aka 9.0.4), and Ingres 2006 release 2 (aka 9.1.0) o…
published 2008-08-05 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3344
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Untrusted search path vulnerability in ingvalidpw in Ingres 2.6, Ingres 2006 release 1 (aka 9.0.4), and Ingres 2006 release 2 (aka 9.1.0) on Linux and HP-UX allows local users to gain privileges via a crafted shared library, related to a "pointer overwrite vulnerability."
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-426 Untrusted Search Path
References
-
ingres.com
/support/security-alert-080108.php
vendor-advisory
-
securitytracker.com
/id?1020614
vdb-entry, third-party-advisory
-
vupen.com
/english/advisories/2008/2292
vdb-entry, third-party-advisory
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=733
third-party-advisory, broken-link
-
secunia.com
/advisories/31398
third-party-advisory
-
vupen.com
/english/advisories/2008/2313
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44181
vdb-entry, third-party-advisory
-
secunia.com
/advisories/31357
third-party-advisory
-
securityfocus.com
/archive/1/495177/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/30512
vdb-entry, third-party-advisory
-
support.ca.com
/irj/portal/anonymous/phpsupcontent?contentID=181989
broken-link
Sources
- CVE List CVE-2008-3357
- NVD CVE-2008-3357
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.