dbcve.org
Lotus DominoApplication · Ibm

CVE-2001-1567

MEDIUM · 5.0 CVSS v2.0 Published 2001-12-31
Fix available
A fix is available. Upgrade to after 5.0.9a or later.
See remediation →
59/100
Remediation priority · Elevated
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 server 5.0.9a and earlier allows remote attackers to bypass security restrictions and view Notes database files and possibly sensitive Notes template files (.ntf) via an HTTP request with a large number of "+" characters before the .nsf file extension, which are converted to spaces by Domino.

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 confidence

Lotus Domino server 5.0.9a and earlier contains a path traversal vulnerability where the server converts a large number of '+' characters to spaces in HTTP request URLs before the .nsf file extension. This allows remote attackers to bypass security restrictions and access Notes database files (.nsf) and potentially sensitive Notes template files (.ntf) that should be protected.

MitigationUpgrade Lotus Domino to a version newer than 5.0.9a, or apply any available security patches from IBM/Lotus. If upgrading is not feasible, review and tighten access control lists (ACLs) on Notes databases and ensure web-only access is properly restricted.

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:= 5.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.7a= 5.0.8= 5.0.9
Lotus Domino ServerApplication
Affected:<= 5.0.9a

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

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

  1. Identify the installed Lotus Domino version
    Run the command 'tell server version' from the Domino server console, or check the version information in the Domino Administrator client under 'Server - Status'. On Windows, also check the 'Program Files\Lotus\Domino\version.ini' file.
    Affected if The version is 5.0.9a or any 5.0.x version (5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.7a, 5.0.8, 5.0.9) or lower.
  2. Verify HTTP service is enabled
    From the Domino Administrator, navigate to Configuration - Server - Current Server Document - Ports - Internet Ports. Check if HTTP is listed and enabled. Alternatively, from the server console, run 'show port HTTP' to see if the HTTP listener is active.
    Affected if HTTP is enabled and the server is listening on port 80 or 443.
  3. Test for web-accessible .nsf databases
    Using a web browser or curl, attempt to access a known .nsf database via HTTP without authentication, for example: 'http://<server>/database.nsf' or 'http://<server>/names.nsf'. If the server returns database content without requiring authentication, the vulnerability may be present.
    Affected if The server returns database content or directory listings for .nsf files without authentication.
  4. Confirm path traversal accessibility
    Attempt to access a protected .nsf or .ntf file using the '+' character padding technique mentioned in the CVE: 'http://server/+...+.nsf' where '+...+' represents multiple plus signs. Check if the server allows access to files that should be protected by ACLs.
    Affected if The server grants access to protected .nsf or .ntf files using the plus-sign padding technique.

If the server is running Lotus Domino 5.0.x or 5.0.9a or earlier AND has HTTP enabled and accessible, the environment is affected by this path traversal vulnerability.

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
Upgrade available Upgrade to a release after 5.0.9a
Interim mitigation

Upgrade Lotus Domino to a version newer than 5.0.9a, or apply any available security patches from IBM/Lotus. If upgrading is not feasible, review and tighten access control lists (ACLs) on Notes databases and ensure web-only access is properly restricted.

Fix this in Lotus Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2001-1567 — 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-2001-1567 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