CVE-2007-6053
First published: Tue Nov 20 2007(Updated: )
IBM DB2 UDB 9.1 before Fixpak 4 does not properly handle use of large numbers of file descriptors, which might allow attackers to have an unknown impact involving "memory corruption." NOTE: the vendor description of this issue is too vague to be certain that it is security-related.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Microsoft Windows Operating System | ||
| Unix | ||
| IBM DB2 Universal Database | <=9.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2007-6053?
The severity of CVE-2007-6053 is considered moderate due to potential memory corruption risks.
How do I fix CVE-2007-6053?
To fix CVE-2007-6053, upgrade to IBM DB2 Universal Database version 9.1 Fixpak 4 or later.
What systems are affected by CVE-2007-6053?
CVE-2007-6053 specifically affects IBM DB2 Universal Database versions prior to Fixpak 4.
What type of vulnerability is CVE-2007-6053?
CVE-2007-6053 is classified as a memory corruption vulnerability.
What impact can CVE-2007-6053 have on systems?
CVE-2007-6053 may allow attackers to exploit memory corruption, leading to undefined behavior or potential system compromise.
- collector/nvd-historical
- agent/references
- agent/type
- agent/event
- agent/last-modified-date
- agent/first-publish-date
- agent/weakness
- agent/remedy
- agent/severity
- agent/author
- agent/description
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel
- vendor/microsoft
- canonical/microsoft windows operating system
- vendor/unix
- canonical/unix
- vendor/ibm
- canonical/ibm db2 universal database
- version/ibm db2 universal database/9.1