LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37248: A vulnerability has been identified in Tecnomatix Plant Simulation V2201 (All versions < V2201.0008), Tecno...

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

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-37248 affects Siemens Tecnomatix Plant Simulation. A malicious PAR file can trigger memory corruption when opened, potentially letting attacker code run as the current user. The issue requires user interaction, so phishing, shared engineering files, or supplier-provided models are the main concern.

Executive priority

Treat this as a high-priority engineering workstation risk, not an internet-facing server emergency. Prioritize teams handling third-party simulation files because compromise could expose sensitive models and provide a foothold in engineering environments.

Technical view

The vulnerable parser performs an out-of-bounds write past an allocated buffer while processing a specially crafted PAR file. Affected releases are Tecnomatix Plant Simulation V2201 before V2201.0008 and V2302 before V2302.0002. CVSS 3.1 is 7.8 with local attack vector, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is limited to organizations running the listed Siemens Tecnomatix Plant Simulation versions, especially engineering environments that exchange PAR files with third parties or across trust boundaries.

Exploitation context

The bundle does not report active exploitation, and KEV is false. The CVSS vector includes proof-of-concept exploit maturity, but the provided sources do not include exploit details. Successful exploitation requires a user to open a crafted PAR file locally.

Researcher notes

Evidence is strongest for version scope, bug class, and impact. The bundle names ZDI-CAN-21155, CWE-787, and Siemens advisory SSA-764801, but does not provide parser internals, exploit artifacts, or confirmed in-the-wild activity.

Mitigation direction

  • Upgrade V2201 installations to V2201.0008 or later.
  • Upgrade V2302 installations to V2302.0002 or later.
  • Review Siemens SSA-764801 for official remediation guidance.
  • Block or quarantine untrusted PAR files until affected systems are upgraded.
  • Limit PAR file exchange to trusted, validated sources.

Validation and detection

  • Inventory Siemens Tecnomatix Plant Simulation installations and exact build versions.
  • Identify users or workflows that open PAR files from external sources.
  • Confirm V2201 systems are not below V2201.0008.
  • Confirm V2302 systems are not below V2302.0002.
  • Check endpoint controls for suspicious activity after opening unexpected PAR files.
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-37248 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-37248Attack 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 Simulation V2201All versions < V2201.0008unknown
SiemensTecnomatix Plant Simulation V2302All versions < V2302.0002unknown
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.