CVE-2022-2825
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on affected installations of Kepware KEPServerEX 6.11.718.0. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of text encoding conversions. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-18411.
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 confidenceA stack-based buffer overflow vulnerability in KEPServerEX 6.11.718.0 allows remote unauthenticated attackers to execute arbitrary code as SYSTEM. The flaw exists in the handling of text encoding conversions where the length of user-supplied data is not properly validated before being copied to a stack-based buffer.
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< 7.612< 6.12< 6.12all versions< 1.4< 6.12< 6.12< 6.12CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the installed product variantDetermine which KEPServerEX-based product is installed on the system from the list: Ge Industrial Gateway Server, Ptc Kepware Kepserverex, Ptc Opc Aggregator, Ptc Thingworx Industrial Connectivity, Ptc Thingworx Kepware Edge, Ptc Thingworx Kepware Server, Rockwellautomation Kepserver Enterprise, or Softwaretoolbox Top ServerAffected if The installed product is any of these eight affected products
-
Check the installed version numberLocate the version information for the installed product (typically found in the application properties, about dialog, or registry) and compare it to the affected version ranges: Ge Industrial Gateway Server < 7.612, PTC Kepware Kepserverex < 6.12, PTC OPC Aggregator < 6.12, PTC Thingworx Industrial Connectivity (all versions), PTC Thingworx Kepware Edge < 1.4, PTC Thingworx Kepware Server < 6.12, Rockwellautomation Kepserver Enterprise < 6.12, Softwaretoolbox Top Server < 6.12Affected if The installed version falls within any of the vulnerable version ranges listed
-
Verify the OPC services are network-accessibleCheck if the OPC server service (OPC UA or OPC DA) is running and bound to a network interface accessible to untrusted networks. Review firewall rules and service binding configurations.Affected if The OPC services are exposed to untrusted network access, as the vulnerability can be exploited by remote unauthenticated attackers
The environment is affected if the installed product is one of the eight listed variants AND the version is below the specified threshold AND the OPC services are network-accessible.
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.
dbcve · scoped1.46.127.612
Apply the vendor patch or update to a patched version of KEPServerEX. If patching is not immediately feasible, restrict network access to the affected KEPServerEX instances and implement compensating controls such as network segmentation.
Industrial Gateway Server: 7.612 | KEPServerEX, Opc Aggregator, Thingworx Kepware Server, Kepserver Enterprise, Top Server: 6.12 | Thingworx Kepware Edge: 1.4
- Identify all affected Kepware products in the environment using the version list
- Download the patched versions from the official PTC/Kepware download portal
- Test the new versions in a non-production environment before production deployment
- Create a complete backup of current configurations
- Schedule a maintenance window for the upgrade
- Stop all Kepware services before upgrading
- Install the fixed versions: Industrial Gateway Server to 7.612; KEPServerEX/Opc Aggregator/Thingworx Kepware Server/Kepserver Enterprise/Top Server to 6.12; Thingworx Kepware Edge to 1.4
- Restore configurations from backup after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2825 — 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-2825 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