dbcve.org
Lotus DominoApplication · Ibm

CVE-2004-0669

HIGH · 7.5 CVSS v2.0 Published 2004-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Lotus Domino 6.5.0 and 6.5.1, with IMAP enabled, allows remote authenticated users to change their quota by using the IMAP setquota command.

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 confidence

Lotus Domino 6.5.0 and 6.5.1 with IMAP enabled contains an authorization flaw where remote authenticated IMAP users can modify their own mailbox quota using the SETQUOTA command, bypassing intended administrative controls over storage limits.

MitigationUpgrade Lotus Domino to a version beyond 6.5.1 that contains the fix, or disable IMAP if not required, or implement network-level access controls restricting IMAP to trusted admin networks only.

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
Lotus DominoApplication
Affected:= 6.5.0= 6.5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Lotus Domino version
    Locate the Domino server program directory and check the version information (typically via domino.exe version or server console command like 'show server')
    Affected if The installed version is 6.5.0 or 6.5.1
  2. Determine if IMAP service is enabled
    Inspect Domino server configuration documents or notes.ini settings for IMAP service status (look for IMAP configuration in Server文档 or TCP/IP port settings)
    Affected if IMAP is enabled and listening on the server
  3. Verify IMAP quota configuration exists
    Check if IMAP quota settings are defined in the Domino IMAP configuration (typically found in the IMAP settings section of the server configuration document)
    Affected if IMAP quota management is configured on the server
  4. Confirm user authentication method for IMAP
    Review Domino IMAP authentication settings to determine if remote users can authenticate to the IMAP service
    Affected if Remote authenticated IMAP users have access to the server

You are affected if your Domino installation is version 6.5.0 or 6.5.1 AND IMAP service is enabled, allowing remote authenticated users to bypass quota controls via SETQUOTA.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Lotus Domino to a version beyond 6.5.1 that contains the fix, or disable IMAP if not required, or implement network-level access controls restricting IMAP to trusted admin networks only.

Fix this in Lotus Domino Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0669 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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