ThingWorx Edge C-SDK: Integer Overflow or Wraparound
CVE-2023-0754 is a critical-severity integer overflow or wraparound vulnerability in ThingWorx Edge C-SDK from PTC, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected ThingWorx Edge C-SDK versions: v2.2.12.1052 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.94% chance of exploitation within 30 days, higher than 87% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of ThingWorx Edge C-SDK you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| PTC | ThingWorx Edge C-SDK | v2.2.12.1052 and earlier | Not stated |
| Microsoft | .NET-SDK | v5.8.4.971 and earlier | Not stated |
| PTC | ThingWorx Edge MicroServer (EMS) | v5.4.10.0 and earlier | Not stated |
| PTC | Kepware KEPServerEX | v6.12 and earlier | Not stated |
| PTC | ThingWorx Kepware Server | v6.12 and earlier | Not stated |
| PTC | ThingWorx Industrial Connectivity | All Versions | Not stated |
| PTC | ThingWorx Kepware Edge | v1.5 and earlier | Not stated |
| Rockwell Automation | KEPServer Enterprise | v6.12 and earlier | Not stated |
| General Electric | Digital Industrial Gateway Server | v7.612 and earlier | Not stated |
| Ptc | Kepware Server | 6.12 and earlier | Not stated |
| Ptc | Kepware Serverex | 6.12 and earlier | Not stated |
| Ptc | Thingworx .net-sdk | 5.8.4.971 and earlier | Not stated |
| Ptc | Thingworx Edge Microserver | 5.4.10.0 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
The affected products are vulnerable to an integer overflow or wraparound, which could allow an attacker to crash the server and remotely execute arbitrary code.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/uscert/ics/advisories/icsa-23-054-01Third Party Advisory, US Government Resource
Other vulnerabilities in ThingWorx Edge C-SDK
- 9.8 Critical severity
Recent Integer Overflow or Wraparound vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.