CVE-2003-0032
First published: Fri Jan 17 2003(Updated: )
Memory leak in libmcrypt before 2.5.5 allows attackers to cause a denial of service (memory exhaustion) via a large number of requests to the application, which causes libmcrypt to dynamically load algorithms via libtool.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Libmcrypt | =2.5.1_r4 | |
| Libmcrypt | =2.5.2 | |
| Libmcrypt | =2.5_.0 | |
| Libmcrypt | =2.5.3 |
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-2003-0032?
CVE-2003-0032 is considered a medium severity vulnerability due to its potential for denial of service through memory exhaustion.
How do I fix CVE-2003-0032?
To fix CVE-2003-0032, you should upgrade to libmcrypt version 2.5.5 or later.
What type of attack does CVE-2003-0032 pertain to?
CVE-2003-0032 pertains to denial of service attacks caused by a memory leak in libmcrypt.
Which versions of libmcrypt are affected by CVE-2003-0032?
CVE-2003-0032 affects libmcrypt versions 2.5.1_r4, 2.5.2, 2.5_.0, and 2.5.3.
What are the consequences of exploiting CVE-2003-0032?
Exploiting CVE-2003-0032 can lead to application instability and downtime due to memory exhaustion.
- agent/references
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/remedy
- agent/author
- agent/severity
- agent/last-modified-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/mcrypt
- canonical/libmcrypt
- version/libmcrypt/2.5.1_r4
- version/libmcrypt/2.5.2
- version/libmcrypt/2.5_.0
- version/libmcrypt/2.5.3