CVE-2005-2175
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 web interface for Lotus Notes mail automatically processes HTML in an attachment without prompting the user to save or open it, which makes it easier for remote attackers to conduct web-based attacks and steal cookies.
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 confidenceThe Lotus Notes web mail interface automatically processes and renders HTML content within attachments without prompting the user to save or open the file. This allows malicious HTML embedded in attachments to execute within the security context of the domain, enabling cookie theft and cross-site scripting attacks.
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 dataall versionsCVSS 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 Notes web interface usageAccess your Lotus Notes server's web mail URL (typically /mail/database.nsf) in a browser to determine if the web interface is enabled and accessibleAffected if The Lotus Notes web mail interface is active and reachable
-
Locate web interface configurationAccess the Domino Administrator client or check the server's notes.ini configuration file for settings related to web attachment handling. Look for parameters controlling automatic rendering of file attachmentsAffected if Automatic HTML rendering in attachments is enabled in the configuration
-
Inspect attachment handling settingsIn the Domino Directory, navigate to the server document and check the 'Internet Protocols' > 'HTTP' > 'DWA Settings' section for options controlling how attachments are handled in the web interfaceAffected if Settings allow automatic processing of HTML content in attachments without user prompt
-
Test HTML attachment behaviorCreate a simple HTML file attachment and send it to a Lotus Notes mail recipient accessing via web interface. Observe whether the browser renders the HTML automatically or prompts for save/open actionAffected if HTML attachments render automatically in the browser without prompting the user to save or open the file
You are affected if the Lotus Notes web mail interface automatically renders HTML content in attachments without prompting the user, allowing script execution within the domain context.
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 dataDisable automatic HTML rendering in the Lotus Notes web interface configuration to require user prompt before opening attachments, and apply any available vendor patches for this issue.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2175 — 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-2005-2175 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