Nomad Server On DominoApplication · Hcltech

CVE-2024-30128

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 1.0.13 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Nomad server on Domino is affected by an open proxy vulnerability in which an unauthenticated attacker can mask their original source IP address. This may enable an attacker to trick the user into exposing 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 · moderate confidence

HCL Nomad server on Domino contains an open proxy vulnerability that allows unauthenticated attackers to route traffic through the server, masking their original source IP address. This could enable malicious actors to bypass IP-based access controls and impersonate trusted sources to trick users into exposing sensitive information.

MitigationImplement strict access controls on the HCL Nomad server, disable open proxy functionality, enable proper authentication for all Nomad services, and apply network-level filtering to restrict outbound connections to authorized destinations.

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
Nomad Server On DominoApplication
Affected:< 1.0.13

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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. Identify HCL Nomad Server version
    Locate the Nomad Server installation and check the version number. This is typically found in the program files, release notes, or the Domino console when Nomad is loaded. Compare your installed version against the affected range of versions prior to 1.0.13.
    Affected if Your installed version is lower than 1.0.13
  2. Confirm HCL Nomad Server is running on Domino
    Check that the Nomad Server component is actually installed and running on your Domino server. This can be verified through the Domino server console, task list, or system process list showing the Nomad task or service.
    Affected if HCL Nomad Server is installed and running on your Domino server
  3. Verify proxy configuration settings
    Examine the Nomad Server configuration files and settings for any proxy-related parameters. Look for configuration that allows the server to act as an open proxy or relay for external connections without authentication.
    Affected if Proxy functionality is enabled and accessible without authentication

You are affected if HCL Nomad Server On Domino version 1.0.13 or higher is NOT installed and the server is configured with accessible proxy functionality that permits unauthenticated relay of external traffic.

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 1.0.13 or later
Fixed in 1.0.13
Interim mitigation

Implement strict access controls on the HCL Nomad server, disable open proxy functionality, enable proper authentication for all Nomad services, and apply network-level filtering to restrict outbound connections to authorized destinations.

Recommended fix High confidence

1.0.13

  1. Backup the current Nomad Server on Domino configuration and data
  2. Stop the Nomad Server service
  3. Download HCL Nomad Server on Domino version 1.0.13 or later from the HCL Support Portal (support.hcltechsw.com)
  4. Install the updated Nomad Server on Domino package using standard HCL installation procedures
  5. After installation, verify that the version has been updated to 1.0.13 or later
  6. Start the Nomad Server service
  7. Confirm the vulnerability is resolved by verifying that the open proxy behavior is no longer present
Caveat Review HCL release notes for version 1.0.13 to check for any compatibility notes with your Domino version

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

Fix this in Nomad Server On Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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