Opcenter Execution Foundation: Heap-based Buffer Overflow
CVE-2024-49775 is a critical-severity heap-based buffer overflow vulnerability in Opcenter Execution Foundation from Siemens, 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. The record lists version V2501.0001 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 1.51% chance of exploitation within 30 days, higher than 75% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Opcenter Execution Foundation to V2501.0001 or a later version.
- Update Opcenter Intelligence to V2501.0001 or a later version.
- Update Opcenter Quality to V2512 or a later version.
- 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 V2501.0001 | V2501.0001 |
| Siemens | Opcenter Intelligence | before V2501.0001 | V2501.0001 |
| Siemens | Opcenter Quality | before V2512 | V2512 |
| Siemens | Opcenter RDnL | before V2410 | V2410 |
| Siemens | SIMATIC PCS neo V4.0 | all versions | Not stated |
| Siemens | SIMATIC PCS neo V4.1 | before V4.1 Update 3 | V4.1 Update 3 |
| Siemens | SIMATIC PCS neo V5.0 | before V5.0 Update 1 | V5.0 Update 1 |
| Siemens | SINEC NMS | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V16 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V17 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V18 | all versions | Not stated |
| Siemens | Totally Integrated Automation Portal (TIA Portal) V19 | all versions | 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 CNA (siemens.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.3 | Critical | CNA (siemens.com) |
| CVSS 3.1 | 9.8 | Critical | CNA (siemens.com) |
Official description
A vulnerability has been identified in Opcenter Execution Foundation (All versions < V2501.0001), Opcenter Intelligence (All versions < V2501.0001), Opcenter Quality (All versions < V2512), Opcenter RDnL (All versions < V2410), SIMATIC PCS neo V4.0 (All versions), SIMATIC PCS neo V4.1 (All versions < V4.1 Update 3), SIMATIC PCS neo V5.0 (All versions < V5.0 Update 1), SINEC NMS (All versions if operated in conjunction with UMC < V2.15), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions), Totally Integrated Automation Portal (TIA Portal) V18 (All versions), Totally Integrated Automation Portal (TIA Portal) V19 (All versions). Affected products contain a heap-based buffer overflow vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to execute arbitrary code.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- 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: total).
- 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
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 7.8 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.