CVE-2005-4869: Null Pointer Dereference
First published: Sat Dec 31 2005(Updated: )
The (1) to_char and (2) to_date function in IBM DB2 8.1 allows local users to cause a denial of service (application crash) via an empty string in the second parameter, which causes a null pointer dereference.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| IBM DB2 Universal Database | =8.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-2005-4869?
CVE-2005-4869 has a moderate severity level as it can lead to a denial of service due to application crashes.
How do I fix CVE-2005-4869?
To fix CVE-2005-4869, avoid using empty strings as the second parameter in the to_char and to_date functions.
Who is affected by CVE-2005-4869?
CVE-2005-4869 affects local users of IBM DB2 version 8.1.
What causes the vulnerability in CVE-2005-4869?
The vulnerability in CVE-2005-4869 is caused by a null pointer dereference when an empty string is passed as the second parameter.
Is CVE-2005-4869 exploitable remotely?
No, CVE-2005-4869 is not remotely exploitable as it requires local access to the IBM DB2 system.
- agent/first-publish-date
- agent/remedy
- agent/type
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/description
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/ibm
- canonical/ibm db2 universal database
- version/ibm db2 universal database/8.1