dbcve.org
DominoApplication · Hcltech

CVE-2023-28010

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-08
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
In some configuration scenarios, the Domino server host name can be exposed. This information could be used to target future attacks.

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 Domino server in certain configuration scenarios exposes the server's hostname. This information disclosure could aid attackers in reconnaissance by revealing internal network naming conventions or valid server identifiers for targeted attacks.

MitigationReview Domino server configuration settings to identify and remediate scenarios that cause hostname exposure. Limit the information returned in server responses and headers.

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:= 12.0.2

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. Identify installed Domino version
    Check the Domino server version using the command 'tell server version' from the Domino server console, or inspect the server's program directory for version information
    Affected if The installed version is exactly 12.0.2 (no other versions are listed as affected)
  2. Inspect HTTP response headers
    Send an HTTP request to the Domino server (e.g., using curl -I https://<server> or a browser's developer tools) and examine all response headers for hostname leakage
    Affected if The Server header or any custom headers expose the server's hostname or internal naming convention
  3. Check HTTP error pages and responses
    Trigger various HTTP responses (e.g., request non-existent pages, authenticate, access APIs) and inspect the returned content for hostname disclosure
    Affected if Error pages, redirects, or API responses contain the server's hostname that should not be publicly visible
  4. Review Domino HTTP configuration
    Examine the Domino HTTP configuration tasks (via 'show http' console command or HTTP task configuration in domino/data/ibmTECHICAL directory) for settings controlling header information
    Affected if HTTP configuration allows hostname or internal network details to be returned in responses

You are affected if running Domino version 12.0.2 AND the server is exposing its hostname in HTTP headers, error pages, or responses that should not contain this information.

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

Review Domino server configuration settings to identify and remediate scenarios that cause hostname exposure. Limit the information returned in server responses and headers.

Recommended fix Moderate confidence

Domino 12.0.3 or later

  1. Check current Domino version by running 'tell http platform version' or viewing the Domino Administrator client
  2. Verify if the hostname exposure scenario applies to your configuration (typically involves specific HTTP configuration settings)
  3. Contact HCL Support to request the specific interim fix (IF) for CVE-2023-28010 if not yet on a fixed release
  4. Alternatively, upgrade to Domino 12.0.3 or later which contains the security fix for this vulnerability
  5. After upgrade, verify the hostname is no longer exposed in the affected configuration scenario by testing HTTP responses
Caveat Standard minor version upgrade; review HCL release notes for any configuration changes between 12.0.2 and 12.0.3

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

Fix this in Domino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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