dbcve.org
DominoApplication · Hcltech

CVE-2022-44750

HIGH · 7.8 CVSS v3.1 Published 2022-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 Domino is susceptible to a stack based buffer overflow vulnerability in lasr.dll in Micro Focus KeyView. This could allow a remote unauthenticated attacker to crash the application or execute arbitrary code via a crafted Lotus Ami Pro file. This is different from the vulnerability described in CVE-2022-44754.  This vulnerability applies to software previously licensed by IBM.

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

Stack-based buffer overflow vulnerability in lasr.dll (Micro Focus KeyView) within HCL Domino allows remote unauthenticated attackers to crash the application or execute arbitrary code via crafted Lotus Ami Pro files.

MitigationApply vendor-released patch for HCL Domino that updates the Micro Focus KeyView library; consider network-level restrictions on Lotus Ami Pro file processing as interim control.

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:= 9.0= 9.0.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 installed HCL Domino version
    Run 'tell server version' from Domino server console, or check the Notes.ini ProductVersion setting, or inspect the domino executable file properties
    Affected if Version is 9.0 or 9.0.1 (exact match to affected versions)
  2. Locate lasr.dll in the installation
    Search for lasr.dll within the HCL Domino installation directory, typically under the 'keyview' or 'bin' folder
    Affected if lasr.dll exists in the Domino installation (vulnerable library present)
  3. Identify KeyView library version
    Check the properties of lasr.dll or associated KeyView files for version information; compare against the version bundled with Domino 9.0/9.0.1
    Affected if KeyView version matches the unpatched library shipped with Domino 9.0 or 9.0.1
  4. Confirm Lotus Ami Pro file processing is enabled
    Check Domino server configuration for KeyView filter settings; verify if lasr.dll is loaded by checking server logs or using process inspection tools while processing a file
    Affected if KeyView/lasr.dll is actively loaded or configured to process attachments including .sam files (Lotus Ami Pro)

Environment is affected if running Domino 9.0 or 9.0.1 with the KeyView lasr.dll library present and Lotus Ami Pro file processing enabled.

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

Apply vendor-released patch for HCL Domino that updates the Micro Focus KeyView library; consider network-level restrictions on Lotus Ami Pro file processing as interim control.

Recommended fix Moderate confidence

HCL Domino 9.0.2 or later (preferably latest 9.0.x, 10.x, 11.x, or 12.x release)

  1. 1. Identify current HCL Domino version by checking Domino Administrator or running 'show server' command
  2. 2. Upgrade HCL Domino from version 9.0 or 9.0.1 to version 9.0.2 or later (recommended: latest available 9.0.x or 10.x/11.x/12.x)
  3. 3. Apply the latest available HCL Domino Interim Fix (IF) that includes security updates for this vulnerability
  4. 4. After upgrade, verify the lasr.dll version in the KeyView directory reflects the patched version
  5. 5. Test with a sample Lotus Ami Pro file to confirm the application handles the file type correctly without crashing
  6. 6. Monitor HCL support pages (support.hcltechsw.com) for any additional security notices or follow-up patches
Caveat Review release notes for the target version for any configuration or compatibility changes before upgrading; newer major versions (10.x/11.x/12.x) may have feature differences from 9.0.x

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

Fix this in Domino Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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