A vulnerability has been identified in Opcenter Execution Discrete (All versions < V3.2), Opcenter Execution Foundation (All versions < V3.2), Opcenter Execution Process (All versions < V3.2), Opcenter Intelligence (All versions < V3.3), Opcenter Quality (All versions < V11.3), Opcenter RD&L (V8.0), SIMATIC IT LMS (All versions < V2.6), SIMATIC IT Production Suite (All versions < V8.0), SIMATIC Notifier Server for Windows (All versions), SIMATIC PCS neo (All versions < V3.0 SP1), SIMATIC STEP 7 (TIA Portal) V15 (All versions < V15.1 Update 5), SIMATIC STEP 7 (TIA Portal) V16 (All versions < V16 Update 2), SIMOCODE ES V15.1 (All versions < V15.1 Update 4), SIMOCODE ES V16 (All versions < V16 Update 1), Soft Starter ES V15.1 (All versions < V15.1 Update 3), Soft Starter ES V16 (All versions < V16 Update 1). Sending multiple specially crafted packets to the affected service could cause a partial remote denial-of-service, that would cause the service to restart itself. On some cases the vulnerability could leak random information from the remote service.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Opcenter_execution_discrete | Siemens | * | 3.2 (excluding) |
| Opcenter_execution_foundation | Siemens | * | 3.2 (excluding) |
| Opcenter_execution_process | Siemens | * | 3.2 (excluding) |
| Opcenter_intelligence | Siemens | * | 3.3 (excluding) |
| Opcenter_quality | Siemens | * | 11.3 (excluding) |
| Opcenter_rd&l | Siemens | 8.0 (including) | 8.0 (including) |
| Simatic_it_lms | Siemens | * | 2.6 (excluding) |
| Simatic_it_production_suite | Siemens | * | 8.0 (excluding) |
| Simatic_notifier_server | Siemens | * | * |
| Simatic_pcs_neo | Siemens | * | 3.0 (excluding) |
| Simatic_pcs_neo | Siemens | 3.0 (including) | 3.0 (including) |
| Simatic_step_7 | Siemens | 15 (including) | 15.1 (excluding) |
| Simatic_step_7 | Siemens | 15.1 (including) | 15.1 (including) |
| Simatic_step_7 | Siemens | 16 (including) | 16 (including) |
| Simatic_step_7 | Siemens | 16-update1 (including) | 16-update1 (including) |
| Simocode_es | Siemens | * | 15.1 (excluding) |
| Simocode_es | Siemens | 15.1 (including) | 15.1 (including) |
| Simocode_es | Siemens | 16 (including) | 16 (including) |
| Soft_starter_es | Siemens | * | 15.1 (excluding) |
| Soft_starter_es | Siemens | 15.1 (including) | 15.1 (including) |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html