dbcve.org
Domino Appdev PackApplication · Hcl

CVE-2023-28015

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 1.0.16 or later.
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
The HCL Domino AppDev Pack IAM service is susceptible to a User Account Enumeration vulnerability.   During a failed login attempt a difference in messages could allow an attacker to determine if the user is valid or not.  The attacker could use this information to focus a brute force attack on valid users.

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

The HCL Domino AppDev Pack IAM service returns different error messages during failed login attempts depending on whether the user account exists, allowing attackers to enumerate valid usernames. Attackers can use this to identify valid users and then focus brute force or credential stuffing attacks on those accounts.

MitigationModify the IAM service to return uniform, generic error messages (e.g., 'Invalid credentials') regardless of whether the username exists, preventing account enumeration.

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 Appdev PackApplication
Affected:< 1.0.16

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 HCL Domino AppDev Pack installation and version
    Locate the AppDev Pack installation directory and check the version file or binary version information. Common locations include the Domino program directory or a dedicated AppDev Pack folder. Look for version metadata in installed binaries or configuration files.
    Affected if The installed version is any version prior to 1.0.16 (e.g., 1.0.15, 1.0.14, 1.0.13, etc.) or if the version cannot be determined but AppDev Pack is present.
  2. Confirm IAM service component is present
    Check for the presence of IAM (Identity and Access Management) service files within the AppDev Pack installation. Look for IAM-specific configuration directories, executable files, or service definitions.
    Affected if The IAM service component is installed as part of the AppDev Pack.
  3. Verify IAM service is running or enabled
    Check system services or processes for any IAM-related services running as part of the Domino environment. Use system service management tools or process listing commands to identify if the IAM service is active.
    Affected if The IAM service is running or configured to start, exposing the authentication endpoint.
  4. Assess network exposure of IAM authentication endpoint
    Identify any network-accessible endpoints that provide IAM-based authentication for the AppDev Pack. Review firewall rules, reverse proxy configurations, or Domino web configuration settings that expose IAM login interfaces.
    Affected if The IAM authentication endpoint is accessible from network locations, allowing external attackers to send login requests.
  5. Test login error message behavior
    Send test authentication requests to the IAM login endpoint with a known non-existent username versus a valid username. Compare the error messages returned in each case. If the error messages differ in wording, timing, or content between non-existent and existing users, the vulnerability is present.
    Affected if The IAM service returns measurably different error messages or response behaviors for non-existent usernames versus valid usernames with incorrect passwords.

You are affected if the HCL Domino AppDev Pack version is below 1.0.16, the IAM service is installed and running, and the login endpoint returns distinct error messages that reveal whether a username exists in the system.

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.16 or later
Fixed in 1.0.16
Interim mitigation

Modify the IAM service to return uniform, generic error messages (e.g., 'Invalid credentials') regardless of whether the username exists, preventing account enumeration.

Recommended fix High confidence

1.0.16

  1. Back up the current Domino AppDev Pack installation and any associated data
  2. Download the fixed version (1.0.16) from the HCL support portal at support.hcltechsw.com
  3. Review the HCL Domino AppDev Pack 1.0.16 release notes for any specific installation or migration requirements
  4. Stop the IAM service before upgrading
  5. Install version 1.0.16 following the standard HCL upgrade procedures for the AppDev Pack
  6. Restart the IAM service after upgrade completion
  7. Verify that the fix is applied by testing login attempts and confirming error messages no longer differ between valid and invalid usernames

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

Fix this in Domino Appdev Pack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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