CVE-2022-44754
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 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-44750. 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 confidenceStack-based buffer overflow in lasr.dll (Micro Focus KeyView) within HCL Domino allows remote unauthenticated attackers to crash the application or execute arbitrary code via a crafted Lotus Ami Pro file.
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= 9.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 installed HCL Domino versionRun 'tell http version' from Domino console or check the Notes.ini ProductVersion setting, or use 'nserver -v' on the server binaryAffected if Version is 9.0 or 9.0.1 (exactly matching these versions)
-
Verify KeyView lasr.dll module presenceSearch for lasr.dll in the Domino installation directory under the keyview or viewer subdirectory, typically found in the Domino program folderAffected if lasr.dll exists and the KeyView filtering module is loaded by Domino
-
Confirm Lotus Ami Pro file parser is availableCheck Domino configuration for KeyView filter settings; look for Ami Pro or 'sam' file type handlers in the KeyView filter configuration filesAffected if Lotus Ami Pro file type is registered with KeyView for parsing
-
Check if Domino accepts remote file uploads or attachmentsReview Domino server document and Web configuration for 'Allow HTTP attachments' or similar settings, and check if Web servers or HTTP tasks accept file submissions from unauthenticated usersAffected if Remote unauthenticated users can submit files to Domino for processing
Environment is affected if running Domino exactly version 9.0 or 9.0.1 AND the KeyView lasr.dll with Lotus Ami Pro parsing is enabled AND the server accepts remote file uploads that trigger KeyView processing.
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 available HCL Domino security patches addressing the KeyView vulnerability; if patches are unavailable, disable or restrict processing of Lotus Ami Pro files and consider network-level filtering of untrusted file uploads.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-44754 — 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-44754 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