CVE-2000-0567
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 · uneditedBuffer overflow in Microsoft Outlook and Outlook Express allows remote attackers to execute arbitrary commands via a long Date field in an email header, aka the "Malformed E-mail Header" vulnerability.
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 confidenceBuffer overflow vulnerability in Microsoft Outlook and Outlook Express allows remote attackers to execute arbitrary commands by sending emails with an excessively long Date field in the email header, leading to potential remote code execution.
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= 97= 98= 2000= 4.0= 4.01= 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Check Microsoft Outlook versionOpen Outlook, go to Help menu, select About Microsoft Outlook. Alternatively, open Control Panel > Add or Remove Programs, locate Microsoft Outlook and note the version number.Affected if The version listed is 97, 98, or 2000 (unpatched)
-
Check Microsoft Outlook Express versionOpen Outlook Express, go to Help menu, select About Outlook Express. Alternatively, check the version in the application's properties or registry key HKLM\Software\Microsoft\Outlook Express\Setup.Affected if The version listed is 4.0, 4.01, or 5.0 (unpatched)
-
Verify email processing is enabledIn Outlook: go to Tools > Options > Security tab or View > Reading pane. In Outlook Express: go to Tools > Options > Security tab. Confirm the client is configured to display emails (HTML or plain text).Affected if Email display is enabled and the client processes incoming messages without stripping malformed headers
-
Confirm the system is not patchedCheck Windows Update history or the installed patches list for security updates released after June 2000 related to Outlook (MS00-037 or subsequent patches). Look for patch KBxxxxx in Add/Remove Programs.Affected if No relevant security patches for this vulnerability are installed
A system is affected if it runs unpatched Outlook versions 97, 98, or 2000, or unpatched Outlook Express versions 4.0, 4.01, or 5.0, and processes incoming email messages.
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 dataApply relevant Microsoft security patches for Outlook and Outlook Express, or upgrade to patched versions of the software. Consider using email gateway filtering to reject messages with malformed headers as an additional defense layer.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0567 — 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-0567 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