CVE-2008-3356: Medium severity actian ingres vulnerability

Published Aug 5, 2008
·
Updated

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.

Affected Software

5 affected components
Ingres Ingres=2006-release_2
Ingres Ingres=2006-release_1
Ingres Ingres=2006-9.0.1
Ingres Ingres=2.6
Ingres Ingres=2006-9.0.4

Event History

Aug 5, 2008
CVE Published
via MITRE·07:20 PM
Data Sourced
via MITRE·07:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2008-3356?

CVE-2008-3356 is considered a medium severity vulnerability due to potential local file overwrite risks.

2

How do I fix CVE-2008-3356?

To fix CVE-2008-3356, ensure that the ownership and permissions of the iivdb.log file are correctly set and validated before any operations.

3

Which versions of Ingres are affected by CVE-2008-3356?

CVE-2008-3356 affects Ingres versions 2.6, 2006 release 1 (9.0.4), and 2006 release 2 (9.1.0).

4

Can local users exploit CVE-2008-3356?

Yes, local users can exploit CVE-2008-3356 to overwrite arbitrary files due to improper validation of log file ownership.

5

What mitigation strategies can be implemented for CVE-2008-3356?

Mitigation for CVE-2008-3356 includes applying patches provided by the vendor and enforcing strict access controls for log files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203