CVE-2004-1521
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEudora 6.2.0.14 does not issue a warning when a user forwards an e-mail message that contains base64 or quoted-printable encoded attachments, which makes it easier for remote attackers to read arbitrary files via spoofed "Converted" headers.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEudora 6.2.0.14 fails to warn users when forwarding emails containing base64 or quoted-printable encoded attachments. Attackers can exploit this by spoofing 'Converted' headers to trick the client into processing malicious content that could expose arbitrary files on the user's system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.2.0.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Eudora installationCheck for Eudora email client installation in typical locations such as C:\Program Files\Qualcomm Eudora\ or via system registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Eudora), or by searching for 'eudora.exe' on the systemAffected if Eudora is installed on the system
-
Identify Eudora versionLocate eudora.exe, right-click and select Properties, or right-click the Eudora shortcut and select Properties to view the Version tab. Alternatively, open Eudora and go to Help > About EudoraAffected if The installed version is exactly 6.2.0.14
-
Inspect forwarded email headersWhen examining a forwarded email with an attachment, view the message headers (in Eudora: Tools > Options > Display > Show Headers > All, or view the raw message source). Look for a 'Converted' header fieldAffected if A 'Converted' header is present on a forwarded message containing base64 or quoted-printable encoded attachments, and the client does not display a security warning before processing
The user is affected if Eudora version 6.2.0.14 is installed AND forwarded emails with encoded attachments are processed without warning, particularly when 'Converted' headers are present in the message.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUsers should upgrade to a patched version of Eudora or migrate to a modern email client that implements proper warnings for encoded content in forwarded messages. Until then, avoid forwarding untrusted emails with attachments.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-1521 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data