CVE-2024-23804
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 · uneditedA vulnerability has been identified in Tecnomatix Plant Simulation V2201 (All versions < V2201.0012), Tecnomatix Plant Simulation V2302 (All versions < V2302.0006). The affected applications contain a stack overflow vulnerability while parsing specially crafted PSOBJ 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 confidenceA stack overflow vulnerability exists in Tecnomatix Plant Simulation when parsing specially crafted PSOBJ files. Successful exploitation allows an attacker to execute arbitrary code in the context of the current process.
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< 2201.0012>= 2302.0, < 2302.0006CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Tecnomatix Plant Simulation installationCheck for the presence of the Siemens Tecnomatix Plant Simulation installation directory, typically found under C:\Program Files\Siemens\Tecnomatix_Plant_Simulation or in the Windows registry under HKLM\SOFTWARE\Siemens\Tecnomatix Plant SimulationAffected if The software is not installed on the system
-
Locate installed version informationNavigate to the installation directory and locate the version file, or check the program's properties in Add/Remove Programs. The version may also be found in the registry key HKLM\SOFTWARE\Siemens\Tecnomatix Plant Simulation\InstallDir or within the main executable file propertiesAffected if Unable to determine the installed version number
-
Compare version against affected rangesCompare your installed version to the affected ranges: any version less than 2201.0012, or any version from 2302.0 up to but not including 2302.0006Affected if Installed version falls within < 2201.0012 or >= 2302.0 and < 2302.0006
-
Confirm PSOBJ file handling is presentVerify that the Plant Simulation installation includes file import capabilities for PSOBJ files, which is a native file format handled by the softwareAffected if PSOBJ file parsing functionality exists in the installation (this is standard functionality in affected versions)
User is affected if Tecnomatix Plant Simulation is installed with a version matching < 2201.0012 or >= 2302.0 to < 2302.0006 and the software can process PSOBJ files
Generated from the published advisory. Verify against your own configuration.
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 · scoped2201.00122302.0006
Update Tecnomatix Plant Simulation to version V2201.0012 or V2302.0006 or later to remediate the vulnerability.
V2201.0012 or V2302.0006 depending on current branch
- 1. Identify the current installed version of Tecnomatix Plant Simulation (help > about or similar)
- 2. If running V2201 branch (any version < V2201.0012), upgrade to V2201.0012
- 3. If running V2302 branch (any version >= 2302.0 but < V2302.0006), upgrade to V2302.0006
- 4. Download the updated version from Siemens support portal or authorized distribution channel
- 5. Install the upgrade following standard Siemens installation procedures
- 6. Verify the installed version matches the target fixed version
- 7. Test that PSOBJ file parsing functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23804 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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