CVE-1999-1448
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 and Eudora Light before 3.05 allows remote attackers to cause a crash and corrupt the user's mailbox via an e-mail message with certain dates, such as (1) dates before 1970, which cause a Divide By Zero error, or (2) dates that are 100 years after the current date, which causes a segmentation fault.
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 and Eudora Light email clients before version 3.05 contain vulnerabilities when processing email messages with malformed date headers. Specifically, dates before 1970 trigger a divide-by-zero error causing a crash, while dates more than 100 years in the future cause a segmentation fault. Both conditions corrupt the user's mailbox.
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<= 3.05<= 3.05CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Identify Eudora installationCheck for the presence of Eudora or Eudora Light by looking in Program Files for 'Eudora' folder, or check Add/Remove Programs in Windows Control PanelAffected if Eudora or Eudora Light is installed on the system
-
Locate the Eudora executableNavigate to the Eudora installation directory and locate eudora.exe, typically found in C:\Program Files\Eudora\ on Windows systemsAffected if eudora.exe exists on the system
-
Determine installed versionRight-click eudora.exe, select Properties, and view the Version tab to read the File Version. Alternatively, open Eudora and go to Help > About Eudora to see the version numberAffected if The version displayed is 3.05 or any version number lower than 3.05 (such as 3.0, 2.x, 1.x)
-
Confirm edition variantCheck whether the installation is Qualcomm Eudora (full version) or Eudora Light (lightweight version) by looking at the program name in the Start Menu or the About dialogAffected if Either Eudora or Eudora Light version 3.05 or lower is installed
If Eudora or Eudora Light version 3.05 or lower is installed, the system is vulnerable to the date header parsing flaw that causes crashes and mailbox corruption when processing emails with dates before 1970 or more than 100 years in the future.
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 dataUpgrade to Eudora version 3.05 or later. Avoid opening emails from untrusted sources with unusual date headers.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1448 — 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-1999-1448 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