CVE-2000-1215
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 · uneditedThe default configuration of Lotus Domino server 5.0.8 includes system information (version, operating system, and build date) in the HTTP headers of replies, which allows remote attackers to obtain sensitive information.
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 confidenceLotus Domino Server 5.0.8, in its default configuration, embeds system information including version number, operating system details, and build date directly into HTTP response headers. This information leakage allows remote attackers to fingerprint the server environment and identify potential vulnerabilities associated with specific versions.
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.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Lotus Domino versionIssue the command 'nserver -version' or 'domino -version' from the Domino bin directory, or check the Program Files/Lotus/Domino folder for version file. Alternatively, examine the HTTP Server banner by running: telnet <server> 80 and sending 'HEAD / HTTP/1.0' followed by two newlines.Affected if The installed version is exactly 5.0.8
-
Capture HTTP response headersSend an HTTP request to the Domino server (e.g., using curl -I http://<server>/ or netcat to port 80) and capture all response headers from the server.Affected if Headers are returned containing system information such as version number, operating system details, or build date in any header field
-
Inspect headers for information leakageExamine the captured headers for fields that reveal: Domino version number, operating system type/version, build date, or patch level. Common headers may appear in Server: or X- header fields.Affected if The Server header or other headers explicitly reveal version, OS, or build details that would aid in fingerprinting the environment
-
Check if this is a default configurationReview the Domino server's HTTP configuration (notes.ini or server document) for any settings that control header verbosity. In a default 5.0.8 installation, this information disclosure is enabled by default.Affected if No configuration changes have been made to suppress HTTP header information disclosure and the default configuration is in use
A user is affected if running Lotus Domino Server 5.0.8 with default configuration where HTTP response headers expose system version, OS details, or build information that could be used for fingerprinting.
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 dataModify the Domino server configuration to disable the inclusion of system information in HTTP headers, or deploy a reverse proxy/web application firewall in front of Domino to strip these headers from outgoing responses.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-1215 — 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-1215 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