CyberSecBulletin
CVE-2023-46285NVD status: Modified

A vulnerability has been identified in Opcenter Execution Foundation (All versions < V2407)…

Published Updated By the CyberSecBulletin desk

CVE-2023-46285 is a high-severity improper input validation 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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Opcenter Execution Foundation to V2407 or a later version.
  2. Update Opcenter Quality to V2312 or a later version.
  3. Update SIMATIC PCS neo to V4.1 or a later version.
  4. Read the advisory on cert-portal.siemens.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensOpcenter Execution Foundationbefore V2407V2407
SiemensOpcenter Qualitybefore V2312V2312
SiemensSIMATIC PCS neobefore V4.1V4.1
SiemensSINEC NMSbefore V2.0 SP1V2.0 SP1
SiemensTotally Integrated Automation Portal (TIA Portal) V14all versionsNot stated
SiemensTotally Integrated Automation Portal (TIA Portal) V15.1all versionsNot stated
SiemensTotally Integrated Automation Portal (TIA Portal) V16all versionsNot stated
SiemensTotally Integrated Automation Portal (TIA Portal) V17before V17 Update 8V17 Update 8
SiemensTotally Integrated Automation Portal (TIA Portal) V18before V18 Update 3V18 Update 3
SiemensSinumerik Integrate Runmyhmi /automotiveNot specified in the recordNot stated
SiemensTotally Integrated Automation Portal14.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; 1815, 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 improper input validation vulnerability that could allow an attacker to bring the service into a Denial-of-Service state by sending a specifically crafted message to 4004/tcp. The corresponding service is auto-restarted after the crash is detected by a watchdog.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • 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).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Opcenter Execution Foundation

All Opcenter Execution Foundation vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.