dbcve.org
Remisol AdvanceApplication · Beckmancoulter

CVE-2022-26237

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-06
Fix available
A fix is available. Upgrade to after 2.0.12.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
The default privileges for the running service Normand Viewer Service in Beckman Coulter Remisol Advance v2.0.12.1 and prior allows non-privileged 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 · high confidence

The Normand Viewer Service in Beckman Coulter Remisol Advance v2.0.12.1 and prior runs with elevated privileges but has insecure file permissions allowing non-privileged users to overwrite service executables and libraries. Attackers can exploit this DLL hijacking or binary planting vulnerability to escalate privileges and access sensitive data.

MitigationRestrict file permissions on service executables and libraries to deny write access for non-privileged users, and reconfigure the service to run with least-privilege principles matching its actual functional requirements.

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
Remisol AdvanceApplication
Affected:<= 2.0.12.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Beckman Coulter Remisol Advance is installed
    Check for Remisol Advance in installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or use 'Get-WmiObject -Class Win32_Product' to list installed software
    Affected if Remisol Advance appears in the installed software inventory
  2. Determine the installed version of Remisol Advance
    Check the version in the Windows Registry under the Remisol Advance uninstall key, or locate the main executable (typically in Program Files or Program Files x86) and right-click to view Properties > Details for the FileVersion
    Affected if The version is 2.0.12.1 or lower (any version <= 2.0.12.1)
  3. Locate the Normand Viewer Service executable
    Search for files named 'Normand' or 'Viewer' in the Remisol Advance installation directory, typically found under C:\Program Files\Beckman Coulter\ or C:\Program Files (x86)\Beckman Coulter\Remisol Advance\
    Affected if The Normand Viewer Service executable exists in the Remisol Advance installation folder
  4. Verify file permissions on service executables and libraries
    Right-click the Normand Viewer Service executable and any associated DLL files, select Properties > Security, and check the permissions for Users or non-admin groups. Alternatively, use 'icacls <filename>' from an elevated command prompt to view effective permissions
    Affected if Users or non-privileged accounts have Write or Full Control permissions on the service executable or its DLLs
  5. Confirm the service runs with elevated privileges
    Open Services (services.msc), locate the Normand Viewer Service, check the 'Log on as' setting, and verify if it runs as LocalSystem, a domain admin, or another privileged account
    Affected if The service is configured to run as LocalSystem, a service account with administrative rights, or any account with privileges beyond what the application functionality requires

A user is affected if Remisol Advance version 2.0.12.1 or lower is installed AND non-privileged users have write access to the Normand Viewer Service executable or its associated libraries.

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
Upgrade available Upgrade to a release after 2.0.12.1
Interim mitigation

Restrict file permissions on service executables and libraries to deny write access for non-privileged users, and reconfigure the service to run with least-privilege principles matching its actual functional requirements.

Fix this in Remisol Advance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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