CVE-2008-5514: Buffer Overflow
Ludwig Nussel reported a flaw in libc-client / uw-imap:
The rfc822outputchar() function in the uw-imap c-client library does not check whether the buffer is already full and may therefore write one byte too much. This leads to a segfault in rfc822outputdata() later due to memcpy with size -1.
Issue was fixed in imap-2007e: Updated: 16 December 2008
imap-2007e is a maintenance release, consisting primarily of bugfixes to problems discovered in the release that affected a small number of users plus a security fix for users of the RFC822BUFFER routines.
Other sources
Off-by-one error in the rfc822outputchar function in the RFC822BUFFER routines in the University of Washington (UW) c-client library, as used by the UW IMAP toolkit before imap-2007e and other applications, allows context-dependent attackers to cause a denial of service (crash) via an e-mail message that triggers a buffer overflow.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
University of Washington UW-IMAPto a version that resolves this vulnerability.Fixed in imap-2007e
Event History
Frequently Asked Questions
What is the severity of CVE-2008-5514?
The severity of CVE-2008-5514 is classified as high due to potential segmentation faults leading to application crashes.
How do I fix CVE-2008-5514?
To fix CVE-2008-5514, upgrade the University of Washington c-client library to a version later than 2007d.
What software is affected by CVE-2008-5514?
CVE-2008-5514 affects various versions of the University of Washington c-client, specifically all versions prior to 2007d.
What type of vulnerability is CVE-2008-5514?
CVE-2008-5514 is a memory corruption vulnerability that can result in buffer overflow issues.
Who reported CVE-2008-5514?
CVE-2008-5514 was reported by Ludwig Nussel.