dbcve.org
TecnomatixApplication · Siemens

CVE-2023-41846

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 2201.0008 / 2302.0002 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 is vulnerable to memory corruption while parsing specially crafted SPP files. This could allow an attacker to execute code in the context of the current process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability is a memory corruption issue in Tecnomatix Plant Simulation when parsing SPP (Simulation Process Optimization) files. A specially crafted SPP file can trigger heap or stack-based memory corruption during parsing, potentially allowing an attacker to achieve arbitrary code execution in the context of the current process due to the lack of proper bounds checking in the file parsing logic.

MitigationApply the vendor-provided patches by updating to Tecnomatix Plant Simulation V2201.0008 or later, or V2302.0002 or later. Until patches are applied, avoid opening SPP files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TecnomatixApplication
Affected:>= 2201, < 2201.0008>= 2302, < 2302.0002

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Tecnomatix Plant Simulation is installed
    Look for the installation in the Windows registry under HKLM\SOFTWARE\Siemens\Tecnomatix\Plant Simulation or check common installation paths such as C:\Program Files\Siemens\Tecnomatix\Plant Simulation
    Affected if Tecnomatix Plant Simulation is installed on the system
  2. Identify the installed version
    Check the version of PlantSimulation.exe located in the installation directory, or query the registry key for the installed version under the Tecnomatix registry path
    Affected if A version number is returned from the installation
  3. Compare version against affected range 2201
    If the installed version starts with 2201 (such as 2201.0, 2201.1, 2201.2, etc.), verify it is less than 2201.0008. Check the full version string including the build number.
    Affected if Installed version is 2201.x and less than 2201.0008
  4. Compare version against affected range 2302
    If the installed version starts with 2302, verify it is less than 2302.0002. Check the full version string including the build number.
    Affected if Installed version is 2302.x and less than 2302.0002

The environment is affected if Tecnomatix Plant Simulation is installed and the identified version falls within 2201.0 through 2201.0007, or 2302.0 through 2302.0001.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2201.0008 / 2302.0002 or later
Fixed in 2201.00082302.0002
Interim mitigation

Apply the vendor-provided patches by updating to Tecnomatix Plant Simulation V2201.0008 or later, or V2302.0002 or later. Until patches are applied, avoid opening SPP files from untrusted sources.

Recommended fix High confidence

Upgrade to Tecnomatix Plant Simulation V2201.0008 or V2302.0002 (depending on your current branch)

  1. Navigate to the Siemens Tecnomatix Plant Simulation download page or Siemens Support portal
  2. Locate and download Tecnomatix Plant Simulation V2201.0008 (for V2201 branch users)
  3. Locate and download Tecnomatix Plant Simulation V2302.0002 (for V2302 branch users)
  4. Verify the downloaded installer matches your current branch (V2201 or V2302)
  5. Back up any existing SPP files and custom configurations
  6. Install the new version following standard Siemens installation procedures
  7. Validate that the installed version matches the target (V2201.0008 or V2302.0002)
  8. Test SPP file parsing to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tecnomatix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41846 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data