Hcl NomadApplication · Hcltech

CVE-2020-4092

MEDIUM · 5.3 CVSS v3.1 Published 2020-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
"If port encryption is not enabled on the Domino Server, HCL Nomad on Android and iOS Platforms will communicate in clear text and does not currently have a user interface option to change the setting to request an encrypted communication channel with the Domino server. This can potentially expose sensitive information including but not limited to server names, user IDs and document content."

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

When port encryption is not enabled on the HCL Domino Server, HCL Nomad mobile clients on Android and iOS communicate with the server in clear text (unencrypted). The client lacks a user interface option to force encrypted communication, meaning the vulnerability can only be remediated server-side by enabling encryption on the Domino server ports.

MitigationEnable TLS/SSL port encryption on the HCL Domino Server to ensure all Nomad mobile client communications are encrypted, preventing exposure of server names, user IDs, and document content.

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
Hcl NomadApplication
Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify HCL Nomad installation and version
    On Android check Settings > Apps > HCL Nomad, or on iOS check Settings > General > iPhone Storage > HCL Nomad to confirm version 1.0.x is installed
    Affected if HCL Nomad version 1.0 through 1.0.8 is installed on mobile devices
  2. Identify connected Domino servers
    On the Nomad client, access the Domino Directory or server document to list all Domino servers that the mobile client connects to
    Affected if Any Domino server is configured as a destination for the Nomad client
  3. Check Domino server port encryption settings
    On the Domino server, inspect the server document in the Domino Directory and verify the port settings under Server > Ports > Internet Ports. Specifically check if 'SSL' or 'TLS' is enabled for the HTTP/IIOP ports that Nomad uses
    Affected if The Domino server ports that Nomad connects to have encryption (TLS/SSL) disabled or set to 'None'
  4. Verify unencrypted communication exists
    Use network capture tools on the mobile device or network to observe traffic between Nomad and the Domino server. Check if port 80/HTTP is used instead of 443/HTTPS, or if the connection lacks TLS handshake
    Affected if Nomad client communicates with the Domino server over unencrypted channels (plain HTTP or non-TLS ports)

Your environment is affected if HCL Nomad version 1.0.x is installed and connects to a Domino server where port encryption is not enabled, resulting in cleartext communication between the mobile client and server.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable TLS/SSL port encryption on the HCL Domino Server to ensure all Nomad mobile client communications are encrypted, preventing exposure of server names, user IDs, and document content.

Fix this in Hcl Nomad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-4092 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