dbcve.org
NotesApplication · Hcltech

CVE-2022-44751

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 Notes 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-44755.  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

A stack-based buffer overflow vulnerability exists in lasr.dll (Micro Focus KeyView) within HCL Notes. An unauthenticated remote attacker can exploit this by delivering a crafted Lotus Ami Pro file, potentially causing application crashes or enabling arbitrary code execution.

MitigationApply vendor patches for HCL Notes when available; until then, restrict opening of untrusted Lotus Ami Pro files and implement email gateway filtering for suspicious attachments.

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
NotesApplication
Affected:= 9.0.1= 10.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 Notes version
    Open HCL Notes and go to File > About HCL Notes, or check the version via the Notes client installation. On Windows, also check Programs and Features for the installed version.
    Affected if The installed version is exactly 9.0.1 or exactly 10.0.1 (note: the = notation indicates these specific versions, not a range).
  2. Locate lasr.dll in the Notes installation directory
    Navigate to the HCL Notes program directory (typically C:\Program Files\HCL\Notes or C:\Program Files (x86)\HCL\Notes) and search for lasr.dll. Also check subdirectories such as \os\win32 or \components\keyview if they exist.
    Affected if lasr.dll is present in the Notes installation directory, indicating the Micro Focus KeyView filter component is installed.
  3. Verify KeyView attachment filtering is enabled
    In HCL Notes, go to File > Preferences > Mail > Internet and check if 'Convert attachments to Domino MIME format' or similar attachment processing options are enabled. Alternatively, check notes.ini for KeyView-related settings (KVFilterEnabled, KeyViewFilter, or similar parameters).
    Affected if KeyView-based attachment processing is enabled, which means lasr.dll will be invoked when parsing supported file types.
  4. Confirm Lotus Ami Pro file type handling
    Check if Notes is configured to process or preview .sam files (Lotus Ami Pro). This can be verified by examining the KeyView filter configuration or notes.ini for file type associations. Test by attempting to preview a Lotus Ami Pro attachment in a Notes email.
    Affected if Lotus Ami Pro file parsing is active in the environment, enabling the attack vector.

You are affected if HCL Notes version 9.0.1 or 10.0.1 is installed, lasr.dll exists, and KeyView/Lotus Ami Pro file processing is enabled, as the vulnerability triggers when a crafted .sam file is parsed by the vulnerable DLL.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for HCL Notes when available; until then, restrict opening of untrusted Lotus Ami Pro files and implement email gateway filtering for suspicious attachments.

Fix this in Notes Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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