Opcenter Execution Foundation: Out-of-bounds Write
CVE-2023-46284 is a high-severity out-of-bounds write vulnerability in Opcenter Execution Foundation from Siemens, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version V2407 as the first without the flaw, so updating Opcenter Execution Foundation to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.91% chance of exploitation within 30 days, higher than 60% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Opcenter Execution Foundation to V2407 or a later version.
- Update Opcenter Quality to V2312 or a later version.
- Update SIMATIC PCS neo to V4.1 or a later version.
- Read the advisory on cert-portal.siemens.com for workarounds and exact fixed builds.
- 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 |
|---|---|---|---|
| Siemens | Opcenter Execution Foundation | before V2407 | V2407 |
| Siemens | Opcenter Quality | before V2312 | V2312 |
| Siemens | SIMATIC PCS neo | before V4.1 | V4.1 |
| Siemens | SINEC NMS | before V2.0 SP1 | V2.0 SP1 |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V14 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V15.1 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V16 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V17 | before V17 Update 8 | V17 Update 8 |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V18 | before V18 Update 3 | V18 Update 3 |
| Siemens | Sinumerik Integrate Runmyhmi /automotive | Not specified in the record | Not stated |
| Siemens | Totally Integrated Automation Portal | 14.0 up to, but not including, 15; 15 up to, but not including, 16; 16 up to, but not including, 17; 17 up to, but not including, 18; 18 | 15, 16, 17, 18 |
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
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (siemens.com).
Official description
A vulnerability has been identified in Opcenter Execution Foundation (All versions < V2407), Opcenter Quality (All versions < V2312), SIMATIC PCS neo (All versions < V4.1), SINEC NMS (All versions < V2.0 SP1), Totally Integrated Automation Portal (TIA Portal) V14 (All versions), Totally Integrated Automation Portal (TIA Portal) V15.1 (All versions), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions < V17 Update 8), Totally Integrated Automation Portal (TIA Portal) V18 (All versions < V18 Update 3). The affected application contains an out of bounds write past the end of an allocated buffer when handling specific requests on port 4002/tcp and 4004/tcp. This could allow an attacker to crash the application. The corresponding service is auto-restarted after the crash.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Opcenter Execution Foundation
- 9.8 Critical severity
Google Brotli Unchecked Return Value Exploited
- 8.1 High severity
PHP Stale Internal Request-State Exploited
- 9.8 Critical severity
PHP Memory Corruption Exploited
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.