ThingWorx Edge C-SDK: Improper Validation of Array Index
CVE-2023-0755 is a critical-severity improper validation of array index 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 11.8% chance of exploitation within 30 days, which is in the top 3.85% of all 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 improper validation of array index, 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: Improper Validation of Array Index
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
How developers prevent this class of flaw
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
- Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.
More Improper Validation of Array Index vulnerabilities (CWE-129)
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 Improper Validation of Array Index vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.