Matrikon Opc ServerApplication · Honeywell

CVE-2022-1261

HIGH · 8.8 CVSS v3.1 Published 2022-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Matrikon, a subsidary of Honeywell Matrikon OPC Server (all versions) is vulnerable to a condition where a low privileged user allowed to connect to the OPC server to use the functions of the IPersisFile to execute operating system processes with system-level privileges.

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 confidence

The Matrikon OPC Server (all versions) contains a privilege escalation vulnerability where a low-privileged user with network access to the OPC server can abuse the IPersisFile interface functions to execute operating system processes with SYSTEM-level privileges, effectively gaining full control of the host.

MitigationRestrict OPC server connectivity to authorized administrative users only, implement strict access control lists, and contact Honeywell Matrikon for available patches or hardening guidance. Consider network segmentation to limit exposure.

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
Matrikon Opc ServerApplication
Affected:all versions

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Confirm Matrikon OPC Server installation
    Check for Matrikon OPC Server in Windows Programs and Features, or search for 'Matrikon' in installed programs directory (typically C:\Program Files\Matrikon or C:\Program Files (x86)\Matrikon)
    Affected if Matrikon OPC Server is present on the system
  2. Identify the OPC Server service account
    Open Services console, locate the Matrikon OPC service, right-click and select Properties, then check the 'Log On' account
    Affected if The service runs under SYSTEM, a local administrator account, or any privileged domain account
  3. Verify network exposure of the OPC server
    Check OPC server configuration for enabled network listeners. Review Windows Firewall rules or third-party firewall for rules allowing inbound connections to OPC server ports (typically DCOM ports 135, and dynamic ports 49152-65535)
    Affected if The OPC server accepts remote connections from network clients
  4. Assess user access to the OPC server
    Review OPC server security settings and Windows user/group permissions on the server. Check if standard users or low-privilege accounts have OPC client access rights
    Affected if Non-administrative or low-privilege users have network access to connect to the OPC server
  5. Verify IPersisFile interface availability
    Check OPC server documentation or configuration for IPersisFile interface exposure. This is typically exposed via DCOM for remote access
    Affected if The IPersisFile interface is enabled and accessible for remote procedure calls

A user is affected if Matrikon OPC Server is installed, runs under a privileged account, and allows network access from low-privileged users who could invoke the IPersisFile interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict OPC server connectivity to authorized administrative users only, implement strict access control lists, and contact Honeywell Matrikon for available patches or hardening guidance. Consider network segmentation to limit exposure.

Fix this in Matrikon Opc Server 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 help mitigating

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-1261 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1261 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