CVE-2022-26239
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 · uneditedThe default privileges for the running service Normand License Manager in Beckman Coulter Remisol Advance v2.0.12.1 and prior allows unprivileged users to overwrite and manipulate executables and libraries. This allows attackers to access sensitive data.
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 confidenceThe Normand License Manager service in Beckman Coulter Remisol Advance v2.0.12.1 and prior runs with elevated privileges but has insecure default file permissions that allow unprivileged users to overwrite or modify service executables and libraries. This insecure permission configuration enables local privilege escalation and potential sensitive data access.
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<= 2.0.12.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Remisol Advance installationCheck for Beckman Coulter Remisol Advance in Windows Programs and Features, or search for the software installation directory typically found under Program Files or Program Files (x86)Affected if The software is installed and version is 2.0.12.1 or lower
-
Determine installed versionLocate version information in the software's About dialog, installation directory, or Windows Registry under HKLM\Software\Beckman Coulter\Remisol AdvanceAffected if Installed version is 2.0.12.1 or any prior version
-
Locate Normand License Manager service filesSearch for files named normand.exe, lmgrd.exe, or similar license manager executables within the Remisol Advance installation directory and subfoldersAffected if The Normand License Manager executable and associated DLL/library files exist on the system
-
Verify service runs with elevated privilegesOpen Services control panel (services.msc), locate the Normand License Manager or Beckman Coulter License Manager service, right-click and check Properties to view the Log On account; also run 'sc qc <service_name>' from command promptAffected if The service is configured to run under Local System, a domain admin account, or any account with elevated privileges
-
Inspect file permissions on service executables and librariesRight-click the Normand License Manager executable and DLL files, select Properties, go to the Security tab, and examine the permissions for Users and Authenticated Users groups; alternatively run 'icacls <filename>' from command promptAffected if Users or Authenticated Users group has Write or Write+Delete permissions on the service executable or library files
A user is affected if Beckman Coulter Remisol Advance version 2.0.12.1 or lower is installed AND unprivileged users have write access to the Normand License Manager service executable or its library files, with the service running under an elevated account.
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 dataRestrict file system permissions on the Normand License Manager's executable and library files to only allow privileged administrators write access, and configure the service to run with minimum necessary privileges.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26239 — 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-26239 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