dbcve.org
Industrial Gateway ServerApplication · Ge

CVE-2022-2848

CRITICAL · 9.1 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 1.4 / 6.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
This 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 heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-16486.

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

A heap-based buffer overflow vulnerability in Kepware KEPServerEX 6.11.718.0 allows remote unauthenticated attackers to execute arbitrary code as SYSTEM. The flaw exists in text encoding conversion handling where user-supplied data length is not validated before being copied to a heap buffer.

MitigationApply vendor patch when available; until then, isolate KEPServerEX systems on restricted network segments and block external access to prevent unauthenticated exploitation.

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
Industrial Gateway ServerApplication
Affected:< 7.612
Kepware KepserverexApplication
Affected:< 6.12
Opc AggregatorApplication
Affected:< 6.12
Thingworx Industrial ConnectivityApplication
Affected:all versions
Thingworx Kepware EdgeWeb browser
Affected:< 1.4
Thingworx Kepware ServerApplication
Affected:< 6.12
Kepserver EnterpriseApplication
Affected:< 6.12
Top ServerApplication
Affected:< 6.12

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify installed product
    Review installed programs on the system to determine if any of these OPC server products are installed: KEPServerEX, Thingworx Industrial Connectivity, Thingworx Kepware Edge, Thingworx Kepware Server, Ge Industrial Gateway Server, Ptc Opc Aggregator, Kepserver Enterprise, or Top Server.
    Affected if Any of the listed affected products is installed.
  2. Check product version
    Locate the version information for the installed OPC server product (typically found in the product's About dialog, help menu, or installation directory), then compare it against the affected version ranges: Ge Industrial Gateway Server < 7.612, Kepserverex/Thingworx Kepware Server/Opc Aggregator/Top Server < 6.12, Thingworx Kepware Edge < 1.4, or Thingworx Industrial Connectivity (all versions).
    Affected if Installed version falls within any of the affected version ranges.
  3. Determine network exposure
    Check if the OPC server is listening on network ports (typically OPC UA on port 4840, or OPC DA on ports 135/49320) and whether these ports are accessible from external or untrusted network segments.
    Affected if The server is network-accessible and accepts unauthenticated connections.
  4. Verify text encoding feature is active
    Review server configuration for any enabled features that perform text encoding conversion, such as custom drivers, user-defined strings, or data type transformation features that process user-supplied text data.
    Affected if Text encoding conversion features or string handling drivers are configured and active.
  5. Review system logs
    Examine Windows Event Logs and application logs for any crash reports, access violations, or异常 errors related to the OPC server process, particularly those occurring during text or string operations.
    Affected if Crashes or access violations are logged in the OPC server application.

The environment is affected if any of the listed OPC server products is installed with a version within the affected ranges and the server is network-accessible to unauthenticated attackers.

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 1.4 / 6.12 / 7.612 or later
Fixed in 1.46.127.612
Interim mitigation

Apply vendor patch when available; until then, isolate KEPServerEX systems on restricted network segments and block external access to prevent unauthenticated exploitation.

Fix this in Industrial Gateway Server Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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