CVE-2004-2620: Medium severity ripmime vulnerability

Published Dec 31, 2004
·
Updated

The MIMEHreadheaders function in ripMIME 1.3.1.0 does not properly handle trailing "\r" and "\n" characters in headers, which leads to a buffer underflow.

Affected Software

1 affected component
Paul L Daniels Ripmime=1.3.1.0

Remediation

Event History

Dec 31, 2004
CVE Published
05:00 AM
Dec 4, 2005
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 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-2004-2620?

CVE-2004-2620 is classified as a medium severity vulnerability due to the potential for buffer underflow.

2

How do I fix CVE-2004-2620?

To fix CVE-2004-2620, upgrade to a newer version of ripMIME that adequately handles trailing characters in headers.

3

What software is affected by CVE-2004-2620?

CVE-2004-2620 affects ripMIME version 1.3.1.0.

4

What type of vulnerability is CVE-2004-2620?

CVE-2004-2620 is a buffer underflow vulnerability caused by improper handling of trailing characters in MIME headers.

5

Can CVE-2004-2620 be exploited remotely?

Yes, CVE-2004-2620 can be exploited remotely if a maliciously crafted MIME header is processed.

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