CVE-2001-0847
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 · uneditedLotus Domino Web Server 5.x allows remote attackers to gain sensitive information by accessing the default navigator $defaultNav via (1) URL encoding the request, or (2) directly requesting the ReplicaID.
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 confidenceLotus Domino Web Server 5.x contains a path traversal or information disclosure vulnerability in its default navigator $defaultNav. Remote attackers can access sensitive information by either URL-encoding the request or directly requesting the ReplicaID, bypassing intended access controls.
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.xCVSS 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 installed Domino Web Server versionCheck the Domino server version using the command 'show server' in the Domino console or inspect the server's Program directory for version files. Compare against the affected range of 5.x.Affected if The installed version is Domino Web Server 5.x (any minor release).
-
Confirm Web Server service is enabledVerify the Domino HTTP task is running. In the Domino console, run 'show task' or check the Server document in the Domino Directory for HTTP enabled status.Affected if HTTP task is enabled and serving web requests on port 80/443.
-
Test $defaultNav navigator accessibilitySend an HTTP GET request to the server root or a known database path appending '/$defaultNav' or '/$defaultNav?OpenNavigator'. For example: http://target/$defaultNavAffected if The request returns navigator content without authentication or returns any database content listing.
-
Test URL-encoded path traversalSend a crafted request with URL-encoded sequences such as '%2e%2e' or encoded null bytes targeting known database paths (e.g., %2e%2e%2fnames.nsf). Observe if the server returns unauthorized content.Affected if URL-encoded requests return sensitive information or database contents that should be protected.
-
Test ReplicaID direct request accessAttempt to access databases by ReplicaID directly via URL: http://target/replicaid?OpenDatabase. Check if any protected databases become accessible without proper credentials.Affected if Direct ReplicaID requests bypass access controls and return sensitive data.
A server is affected if it runs Domino Web Server 5.x with HTTP enabled and the $defaultNav navigator or direct ReplicaID requests are accessible without proper authentication.
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 dataGiven this affects Domino 5.x (circa 2001), the primary remediation is to upgrade to a supported Domino version with current patches. If legacy systems must remain in service, implement strict network segmentation and disable the default navigator access patterns.
- 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-2001-0847 — 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-2001-0847 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