A vulnerability has been identified in JT2Go (All versions < V14.3.0.1), Teamcenter Visualization V13.3 (All versions < V13.3.0.12), Teamcenter Visualization V14.0 (All versions), Teamcenter Visualization V14.1 (All versions < V14.1.0.11), Teamcenter Visualization V14.2 (All versions < V14.2.0.6), Teamcenter Visualization V14.3 (All versions < V14.3.0.1), Tecnomatix Plant Simulation V2201 (All versions < V2201.0010), Tecnomatix Plant Simulation V2302 (All versions < V2302.0004). The affected application contains a type confusion vulnerability while parsing WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-20826)
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jt2go | Siemens | * | 14.3.0.1 (excluding) |
| Teamcenter_visualization | Siemens | 13.3.0 (including) | 13.4.0.12 (excluding) |
| Teamcenter_visualization | Siemens | 14.0 (including) | 14.1.0.11 (excluding) |
| Teamcenter_visualization | Siemens | 14.2 (including) | 14.2.0.6 (excluding) |
| Teamcenter_visualization | Siemens | 14.3 (including) | 14.3.0.1 (excluding) |
| Tecnomatix_plant_simulation | Siemens | 2201.0 (including) | 2201.0010 (excluding) |
| Tecnomatix_plant_simulation | Siemens | 2302.0 (including) | 2302.0004 (excluding) |
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access. While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways. This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.