CVE-2000-0284
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 University of Washington imapd version 4.7 allows users with a valid account to execute commands via LIST or other commands.
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 in University of Washington imapd version 4.7 allows authenticated users with valid accounts to execute arbitrary commands via LIST or other commands due to insufficient bounds checking in the IMAP server daemon.
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= 12.264CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 if UW imapd is installedRun 'rpm -qa | grep -i uw-imap' or 'dpkg -l | grep -i imap' to check for University of Washington IMAP packages. Alternatively, check for the imapd binary location with 'which imapd' or look in /usr/lib/imapd/Affected if UW imapd package or binary is present on the system
-
Determine the installed imapd versionRun 'rpm -q uw-imap' or check the version string displayed by the IMAP server banner using 'telnet localhost 143' or 'openssl s_client -connect localhost:993'Affected if The version reported is 4.7 or the package version equals 12.264
-
Check if the IMAP service is exposed and accessibleVerify the IMAP daemon is listening on port 143 (IMAP) or port 993 (IMAPS) using 'netstat -tlnp | grep -E "143|993"' or 'ss -tlnp | grep -E "143|993"'Affected if The IMAP service is listening on standard ports and accepts connections
-
Verify user authentication is enabledCheck the imapd configuration files (typically /etc/imapd.conf or similar) for 'authdaemon' or 'login' settings, or attempt to log in with a valid system user account via an IMAP client or manual telnet/ssl connectionAffected if Local user authentication is permitted on the IMAP server
The system is affected if UW imapd version 4.7 (package version 12.264) is installed, the IMAP service is running, and user authentication is enabled, allowing authenticated remote attackers to potentially execute arbitrary commands via buffer overflow in LIST or other commands.
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 a patched version of UW imapd (4.7.beta or later) or migrate to a supported IMAP server implementation such as Courier-IMAP or Dovecot.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0284 — 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-0284 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