Security readout for executives and security teams
Plain-English summary
This affects Siemens Tecnomatix Plant Simulation versions before V2201.0006. A malicious SPP project file can corrupt memory when opened, potentially running attacker-controlled code as the user running the application.
Executive priority
Treat as high priority for teams using Siemens Plant Simulation, especially where external model files are exchanged. It is not described as remotely wormable, but compromise of engineering workstations can affect sensitive designs and operations.
Technical view
The issue is CWE-787 out-of-bounds write during SPP file parsing. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on engineering workstations or build environments using Tecnomatix Plant Simulation before V2201.0006 and handling SPP files from email, shared drives, vendors, or partners.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. The CVSS temporal vector indicates proof-of-concept exploit maturity. Successful exploitation requires a user or workflow to open a specially crafted SPP file.
Researcher notes
Focus validation on version exposure and SPP file ingestion paths. The available sources identify the vulnerable parser behavior and affected version range, but do not provide detailed indicators, active exploitation evidence, or alternate mitigations.
Mitigation direction
- Upgrade Tecnomatix Plant Simulation to V2201.0006 or later.
- Review Siemens advisory SSA-847261 for current vendor guidance.
- Avoid opening SPP files from untrusted or unexpected sources.
- Use endpoint controls to restrict risky file delivery paths.
Validation and detection
- Inventory Tecnomatix Plant Simulation installations and versions.
- Confirm all installations are V2201.0006 or later.
- Identify business workflows that import SPP files from external parties.
- Check endpoint telemetry for unexpected SPP file handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-24979 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS: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 scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://cert-portal.siemens.com/productcert/pdf/ssa-847261.pdfCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.