CVE-2022-26235
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 · uneditedA vulnerability was discovered in the Remisol Advance v2.0.12.1 and below for the Normand Message Server. On installation, the permissions set by Remisol Advance allow non-privileged users to overwrite and/or manipulate executables and libraries that run as the elevated SYSTEM user on Windows.
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 confidenceThis is a local privilege escalation vulnerability in Remisol Advance v2.0.12.1 and below. The installation process sets overly permissive file permissions on executables and libraries used by the Normand Message Server, allowing non-privileged users to overwrite or manipulate these files. Since these files execute with SYSTEM-level privileges, an attacker with regular user access can replace them with malicious code to gain elevated privileges.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Check if Remisol Advance is installedLook for Remisol Advance installation directory, commonly under C:\Program Files\Beckm Coulter\Remisol Advance or similar paths. Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Remisol Advance entry.Affected if No Remisol Advance entry found means not affected by this CVE.
-
Verify installed versionLocate the Remisol Advance installation and check the version. Look in the installation directory for version information or check the Windows Registry uninstall entry for the version number.Affected if Installed version is 2.0.12.1 or lower means potentially affected.
-
Locate Normand Message Server filesIn the Remisol Advance installation directory, identify executables (.exe) and libraries (.dll) associated with the Normand Message Server component. These are the files that run with SYSTEM privileges.Affected if If Normand Message Server executables and libraries exist in the installation directory, check their permissions.
-
Inspect file permissions on executables and librariesRight-click on the Normand Message Server executables and DLLs, go to Properties > Security, and examine the permissions. Check which users or groups have Write or Modify access to these files.Affected if Non-privileged users (such as Authenticated Users or standard users) have Write or Modify permissions on these files means they are affected by this vulnerability.
-
Check if files run with elevated privilegesExamine the service configuration for Normand Message Server in Windows Services (services.msc). Check the service properties to see if it runs as SYSTEM or another elevated account.Affected if Service runs as SYSTEM or LocalSystem account, and non-privileged users have write access to the executable files, confirms the vulnerability is exploitable.
A user is affected if Remisol Advance version 2.0.12.1 or lower is installed AND non-privileged users have Write or Modify permissions on Normand Message Server executables or libraries that run as SYSTEM.
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 dataCorrect file permissions on the Remisol Advance installation directory to restrict write access for non-privileged users on executables and libraries, or apply vendor-supplied patch.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26235 — 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-26235 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