dbcve.org
Domino R5 ClientApplication · Lotus

CVE-2001-0130

HIGH · 10.0 CVSS v2.0 Published 2001-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in HTML parser of the Lotus R5 Domino Server before 5.06, and Domino Client before 5.05, allows remote attackers to cause a denial of service and possibly execute arbitrary commands via a malformed font size specifier.

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

Buffer overflow vulnerability in the HTML parser of IBM Lotus R5 Domino Server (before 5.06) and Domino Client (before 5.05) allows remote attackers to trigger the overflow via malformed font size specifiers in HTML content, potentially enabling denial of service or arbitrary command execution.

MitigationUpgrade Lotus Domino Server to version 5.06 or later and Domino Client to 5.05 or later. If running these legacy systems is unavoidable, implement strict network filtering to block untrusted HTML content from reaching the affected services.

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
Domino R5 ClientApplication
Affected:= 5.04= 5.05
Domino R5 ServerApplication
Affected:= 5.04= 5.05= 5.06

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 Domino version
    Open the Domino Administrator client, or check the server console for version by typing 'show server' or checking the program directory for version files. On Windows, check the registry under HKEY_LOCAL_MACHINE\Software\Lotus\Domino or examine the version.txt in the Domino program folder.
    Affected if The installed version is 5.04 or 5.05 (or any version before 5.06 for Server, or before 5.05 for Client)
  2. Confirm Domino component type
    Determine whether the installation is a Domino Server or Client by reviewing the installed program type and running services.
    Affected if The system is a Domino Server version 5.04-5.05 or a Domino Client version 5.04-5.05
  3. Check if HTML rendering is active
    Domino processes HTML by default in web serving (HTTP task), email rendering, and rich text field display. Verify the HTTP task is running on servers: type 'show task' at the server console. For clients, check if HTML email preview or embedded HTML viewing is enabled.
    Affected if HTTP task is enabled on a Server, or email/rich text features are used on a Client (default enabled states)
  4. Assess network exposure
    Review firewall rules and network accessibility of the Domino HTTP port (default 80). Check if the server is reachable from untrusted networks using telnet or port scanning to confirm external attack surface.
    Affected if The Domino HTTP service is accessible from network segments beyond trusted internal users

You are affected if you are running Domino R5 Server versions 5.04 or 5.05, or Domino R5 Client versions 5.04 or 5.05, with HTTP or email processing enabled and network accessibility.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Lotus Domino Server to version 5.06 or later and Domino Client to 5.05 or later. If running these legacy systems is unavoidable, implement strict network filtering to block untrusted HTML content from reaching the affected services.

Recommended fix High confidence

Lotus Domino R5 Server 5.06 or later; Lotus Domino R5 Client 5.05 or later

  1. Identify all Lotus Domino R5 Servers in the environment and verify their versions (5.04, 5.05, or 5.06 are vulnerable)
  2. Identify all Lotus Domino R5 Clients in the environment and verify their versions (5.04 and 5.05 are vulnerable)
  3. Plan upgrade to Domino Server 5.06 or later for all affected servers
  4. Plan upgrade to Domino Client 5.05 or later for all affected clients
  5. Schedule a maintenance window for the upgrade
  6. Back up all Domino databases and configuration files before upgrading
  7. Upgrade Domino Server to version 5.06 or later
  8. Upgrade Domino Client to version 5.05 or later
Caveat Upgrading from R5 to later versions may require testing of existing applications and databases for compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Domino R5 Client Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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