LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24981: A vulnerability has been identified in Tecnomatix Plant Simulation (All versions < V2201.0006).

A vulnerability has been identified in Tecnomatix Plant Simulation (All versions < V2201.0006). The affected application contains an out of bounds write past the end of an allocated buffer while parsing a specially crafted SPP file. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-19791)

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Siemens Tecnomatix Plant Simulation can be compromised if a user opens a malicious SPP file. The flaw is memory corruption that may let an attacker run code with the user's privileges. Organizations using Plant Simulation in engineering or manufacturing workflows should update affected installations and limit untrusted SPP file handling.

Executive priority

Prioritize remediation for engineering and manufacturing teams using Tecnomatix Plant Simulation. This is high severity because malicious project files could lead to code execution, but urgency is reduced by required user interaction and lack of cited active exploitation.

Technical view

CVE-2023-24981 is a CWE-787 out-of-bounds write in Tecnomatix Plant Simulation before V2201.0006 during SPP file parsing. CVSS 3.1 is 7.8 high, with local attack vector, low complexity, no privileges required, and user interaction required. Successful exploitation could execute code in the current process.

Likely exposure

Exposure is limited to systems running Siemens Tecnomatix Plant Simulation versions earlier than V2201.0006, especially workstations that receive or open SPP files from external parties, shared project repositories, email, or supplier/customer exchanges.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires convincing a user or workflow to parse a specially crafted SPP file, making phishing, file-sharing, and supply-chain project exchange relevant scenarios.

Researcher notes

Focus validation on version exposure and SPP file trust boundaries. The public description identifies parser memory corruption but does not provide complete exploit details. Avoid assuming network exploitability; the CVSS vector indicates local attack vector with user interaction required.

Mitigation direction

  • Upgrade Tecnomatix Plant Simulation to V2201.0006 or later.
  • Review Siemens advisory SSA-847261 for vendor-specific guidance.
  • Restrict opening SPP files from untrusted or external sources.
  • Apply endpoint controls to engineering workstations handling simulation files.
  • Treat unexpected SPP attachments or downloads as suspicious.

Validation and detection

  • Inventory Tecnomatix Plant Simulation installations and installed versions.
  • Confirm no production workstation remains below V2201.0006.
  • Review file-ingress paths for SPP files from third parties.
  • Check whether engineering users receive SPP files by email or shared portals.
  • Verify vendor update deployment through software management records.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24981 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-24981Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiemensTecnomatix Plant SimulationAll versions < V2201.0006unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.