dbcve.org
Kepware KepserverexApplication · Ptc

CVE-2023-29445

HIGH · 7.8 CVSS v3.1 Developing Published 2024-01-10
Fix available
A fix is available. Upgrade to after 8.5 or later.
See remediation →
80/100
Remediation priority · High
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
An uncontrolled search path element vulnerability (DLL hijacking) has been discovered that could allow a locally authenticated adversary to escalate privileges to SYSTEM.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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
Kepware KepserverexApplication
Affected:>= 6.0.2107.0, <= 6.14.263.0
Thingworx Kepware ServerApplication
Affected:>= 6.8, <= 6.14.263.0
Thingworx Industrial ConnectivityApplication
Affected:>= 8.0, <= 8.5

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to a release after 8.5
Recommended fix Moderate confidence

KepServerEX/Thingworx Kepware Server: version 6.14.264.0 or later | Thingworx Industrial Connectivity: version 8.6 or later

  1. 1. Identify the currently installed KepServerEX, Thingworx Kepware Server, or Thingworx Industrial Connectivity version.
  2. 2. Download the latest version of the affected PTC Kepware product from the official PTC Customer Support portal (support.ptc.com) or the PTC download center.
  3. 3. Before upgrading, ensure you have a complete backup of the current configuration and project files.
  4. 4. Stop all Kepware services on the affected system before performing the upgrade.
  5. 5. Install the new version (version 6.14.264.0 or later for KepServerEX/Thingworx Kepware Server; version 8.6 or later for Thingworx Industrial Connectivity).
  6. 6. After installation, restore the configuration from the backup.
  7. 7. Restart the Kepware services and verify the installation was successful.
  8. 8. Validate that the DLL hijacking vulnerability is no longer present by confirming the application loads only from secure, expected paths.
Caveat Review PTC release notes for the new version for any configuration or feature changes that may affect your existing setup

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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