CVE-2022-44755
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 · uneditedHCL 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-44751. 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 · moderate confidenceStack-based buffer overflow in lasr.dll (Micro Focus KeyView filter) in HCL Notes allows remote unauthenticated attackers to execute arbitrary code or crash the application via crafted Lotus Ami Pro files.
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= 9.0.1= 10.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HCL Notes installation and versionOpen HCL Notes and go to File > HCL Notes > About HCL Notes, or check Add/Remove Programs (Windows) for HCL Notes version informationAffected if Installed version is 9.0.1 or 10.0.1 exactly as listed in affected versions
-
Locate the KeyView filter component lasr.dllSearch for lasr.dll in the HCL Notes installation directory, typically under the 'notes' or 'framework' subdirectory. Common paths include C:\Program Files\HCL\Notes\ or C:\Program Files (x86)\HCL\Notes\Affected if The file lasr.dll exists in the HCL Notes installation directory
-
Verify KeyView filter is enabled for file parsingIn HCL Notes, go to File > Preferences > Trust Settings > KeyView Options (or similar path depending on version) to check if KeyView filter is enabled for parsing attachmentsAffected if KeyView filter for file parsing is enabled and allows processing of attachment files
-
Confirm Lotus Ami Pro file association capabilityCheck if Notes can handle or preview .sam files (Lotus Ami Pro format). This may be visible in File > Preferences > Basic Notes Client Configuration or by attempting to preview a .sam attachmentAffected if Lotus Ami Pro file handling or preview capability is available in the Notes client
User is affected if HCL Notes version 9.0.1 or 10.0.1 is installed AND the KeyView filter component (lasr.dll) is present with Lotus Ami Pro file handling enabled
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches from HCL for Notes/KeyView when available; restrict opening of untrusted Lotus Ami Pro files until patch is applied.
- Consultation2.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,976.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44755 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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