dbcve.org
DominoApplication · Hcltech

CVE-2020-14260

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-02
Fix available
A fix is available. Upgrade to after 11.0.1 or later.
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
HCL Domino is susceptible to a Buffer Overflow vulnerability in DXL due to improper validation of user input. A successful exploit could enable an attacker to crash Domino or execute attacker-controlled code on the server system.

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

HCL Domino contains a buffer overflow vulnerability in its DXL (Domino XML) functionality due to improper validation of user-supplied input. An attacker can exploit this by sending specially crafted DXL data to crash the Domino server or achieve remote code execution with the privileges of the Domino service account.

MitigationApply the HCL Domino security patch for CVE-2020-14260. If a patch is unavailable, restrict or disable DXL functionality and limit network exposure of Domino servers until the fix can be applied.

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
DominoApplication
Affected:>= 9.0.0, <= 9.0.1>= 10.0.0, <= 10.0.1>= 11.0.0, <= 11.0.1

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Determine installed HCL Domino version
    Run the Domino console command 'show server' or check the server's version through Domino Administrator. Look for the exact version number displayed in the output.
    Affected if The version shown is 9.0.0 through 9.0.1, 10.0.0 through 10.0.1, or 11.0.0 through 11.0.1 (or any combination within these ranges).
  2. Check if DXL is enabled on the server
    Open Domino Administrator and navigate to Configuration > Server > All Server Documents. Locate the server's document and check the settings under the DXL section, or inspect the notes.ini file for DXL-related configuration parameters.
    Affected if DXL processing is enabled or the server accepts DXL requests.
  3. Verify DXL network exposure
    Check Domino server document for HTTP, DIIOP, or other listener configurations that accept DXL input. Use Domino Administrator to review which network ports and services are listening.
    Affected if DXL functionality is exposed over the network on open ports accessible to potential attackers.
  4. Confirm DXL importer is configured
    Examine the Domino Directory (names.nsf) for DXL importer configuration settings, or review server console logs for recent DXL import activity.
    Affected if DXL importer is configured and active on the server.

The server is affected if it runs any Domino version between 9.0.0-9.0.1, 10.0.0-10.0.1, or 11.0.0-11.0.1 AND has DXL functionality enabled or exposed.

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

Apply the HCL Domino security patch for CVE-2020-14260. If a patch is unavailable, restrict or disable DXL functionality and limit network exposure of Domino servers until the fix can be applied.

Recommended fix High confidence

Upgrade to Domino 9.0.2+/10.0.2+/11.0.2+ (latest Feature Pack for your release line)

  1. 1. Identify the current HCL Domino version by running 'show server' or checking server document
  2. 2. Determine which major version line you are on (9.0.x, 10.0.x, or 11.0.x)
  3. 3. For Domino 9.0.x: Upgrade to Domino 9.0.2 or later (recommend latest 9.0.1 FP10)
  4. 4. For Domino 10.0.x: Upgrade to Domino 10.0.2 or later (recommend latest 10.0.1 FP4)
  5. 5. For Domino 11.0.x: Upgrade to Domino 11.0.2 or later (recommend latest 11.0.1 FP2)
  6. 6. Before upgrading in production, test the upgrade in a staging environment
  7. 7. After upgrade, verify DXL functionality works correctly
  8. 8. Apply any additional interim fixes (IF) released after the feature pack
Caveat Feature Pack upgrades are generally backward compatible but test in non-production first; review HCL release notes for any configuration changes

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

Fix this in Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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