CVE-2000-0105
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 · uneditedOutlook Express 5.01 and Internet Explorer 5.01 allow remote attackers to view a user's email messages via a script that accesses a variable that references subsequent email messages that are read by the client.
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 · moderate confidenceA script-based vulnerability in Outlook Express 5.01 and Internet Explorer 5.01 allows remote attackers to read a user's email messages. The attack works through a script that accesses variables referencing subsequent email messages read by the client, enabling unauthorized disclosure of email content.
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= 5.0CVSS 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.
-
Verify Outlook Express versionOpen Outlook Express and go to Help > About, or right-click the Outlook Express icon and select Properties to view the installed version numberAffected if The installed version is 5.0 or 5.01 (the only affected versions per this CVE)
-
Confirm Internet Explorer versionOpen Internet Explorer and go to Help > About to check the IE version installed alongside Outlook ExpressAffected if Internet Explorer 5.01 is present, as the vulnerability requires this specific IE version in combination with Outlook Express
-
Check script execution settingIn Internet Explorer, go to Tools > Internet Options > Security > Custom Level, and review the 'Active scripting' settingAffected if Active scripting is enabled, which is required for the malicious script to execute and access email message variables
-
Inspect HTML email renderingIn Outlook Express, go to Tools > Options > Security and check if 'HTML mail' or 'Read all messages in HTML' is enabledAffected if HTML email rendering is turned on, allowing embedded scripts in emails to execute
-
Review email preview paneIn Outlook Express, go to View > Preview Pane to determine if the preview pane is activeAffected if The preview pane is enabled, as it may facilitate automatic script execution when viewing malicious emails
A user is affected if they run the exact combination of Outlook Express 5.0 or 5.01 with Internet Explorer 5.01, with Active Scripting and HTML email rendering enabled.
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 from the obsolete Outlook Express 5.01 and Internet Explorer 5.01 to modern, currently-supported email clients and browsers, as these 2000-era products are no longer patched and contain known script-based vulnerabilities.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0105 — 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-2000-0105 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