dbcve.org
Domino LeapApplication · Hcltech

CVE-2022-42449

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-30
Fix available
A fix is available. Upgrade to 1.1.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Unsafe default file type filter policy in HCL Domino Volt allows upload of .html file and execution of unsafe JavaScript in deployed applications

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 Volt has an unsafe default file type filter policy that allows users to upload .html files. When these uploaded .html files are deployed within applications, the JavaScript within them can execute in users' browsers, leading to stored cross-site scripting (XSS) attacks.

MitigationConfigure file type filters to block .html file uploads in Domino Volt applications, or restrict allowed file types to safe formats that cannot contain executable script 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
Domino LeapApplication
Affected:>= 1.0, < 1.1.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check HCL Domino Leap version
    Locate the installed Domino Leap version through the product's About page, release documentation, or system information panel. Common paths include the product's installation directory or admin console.
    Affected if The installed version is 1.0.x or any version between 1.0 and 1.1.1 (excluding 1.1.1)
  2. Locate file type filter policy configuration
    Access the Domino Leap admin console or application settings where file upload restrictions are defined. Look for policies controlling permitted file extensions in application settings.
    Affected if A file type filter policy exists with default settings (no custom restrictions applied)
  3. Inspect allowed file types list
    Review the list of permitted file extensions in the upload configuration. Check whether .html or .htm extensions are explicitly included in the allowed types.
    Affected if .html or .htm files are present in the allowed file extensions list
  4. Verify application file upload feature is enabled
    Check if any Domino Leap applications have the file upload control or attachment feature enabled and accessible to end users.
    Affected if File upload capability is available to application users and the file type filter permits .html uploads

A user is affected if running Domino Leap version 1.0 through 1.1.0 and the file type filter policy defaults to allowing .html file uploads in any deployed application.

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.1.1 or later
Fixed in 1.1.1
Interim mitigation

Configure file type filters to block .html file uploads in Domino Volt applications, or restrict allowed file types to safe formats that cannot contain executable script content.

Recommended fix High confidence

HCL Domino Leap 1.1.1

  1. Back up the current HCL Domino Leap installation and all applications data
  2. Review HCL Domino Leap 1.1.1 release notes and system requirements at support.hcl-software.com
  3. Download the HCL Domino Leap 1.1.1 update package from the HCL Support Portal
  4. Stop the Domino Leap server services before applying the update
  5. Install HCL Domino Leap version 1.1.1 following the standard HCL installation/upgrade documentation
  6. Restart the Domino Leap server services after installation
  7. Verify the file upload filter now blocks .html file types by default
  8. Test that legitimate application functionality remains operational
Caveat Review release notes for any breaking changes or configuration changes required when upgrading from version 1.0.x to 1.1.1

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

Fix this in Domino Leap 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-2022-42449 — 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-2022-42449 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