CVE-2024-52567
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 Teamcenter Visualization V14.2 (All versions < V14.2.0.14), Teamcenter Visualization V14.3 (All versions < V14.3.0.12), Teamcenter Visualization V2312 (All versions < V2312.0008), Teamcenter Visualization V2406 (All versions < V2406.0005), Tecnomatix Plant Simulation V2302 (All versions < V2302.0018), Tecnomatix Plant Simulation V2404 (All versions < V2404.0007). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-24237)
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 confidenceOut-of-bounds read vulnerability in Teamcenter Visualization and Tecnomatix Plant Simulation when parsing WRL (VRML) files. The parser reads past the end of an allocated structure, which could be exploited for code execution 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< 2302.0018>= 2404.0, < 2404.0007CVSS 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.
-
Identify installed Siemens productCheck if Teamcenter Visualization or Tecnomatix Plant Simulation is installed on the system. Look for installation directories such as C:\Program Files\Siemens\Teamcenter12 or C:\Program Files\Siemens\Tecnomatix_Plant_Simulation, or check Add/Remove Programs for Siemens software.Affected if Either Teamcenter Visualization or Tecnomatix Plant Simulation is installed.
-
Determine installed version of Tecnomatix Plant SimulationLocate the Tecnomatix Plant Simulation installation directory and check for version information in file properties or an about dialog. Common paths include the main executable or a version file within the installation folder.Affected if The installed version is less than 2302.0018, OR is 2404.0 through 2404.0006.
-
Determine installed version of Teamcenter VisualizationLocate the Teamcenter Visualization installation directory and check for version information. The affected version ranges can be inferred from the fixed versions (V14.2.0.14, V14.3.0.12, V2312.0008, V2406.0005) - any version prior to these fixes is potentially affected.Affected if The installed version is prior to V14.2.0.14, V14.3.0.12, V2312.0008, or V2406.0005.
-
Verify WRL file parsing capabilityConfirm that the WRL (VRML) file parser module is available and accessible within the installed software. This is typically a built-in visualization component used for 3D model import.Affected if The software includes WRL/VRML file parsing functionality, which is enabled by default in these products.
If either Teamcenter Visualization or Tecnomatix Plant Simulation is installed with a version matching the affected ranges and WRL file parsing is available, the environment is vulnerable to out-of-bounds read exploitation when parsing specially crafted WRL 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 · scoped2302.00182404.0007
Upgrade to the patched versions of Teamcenter Visualization (V14.2.0.14, V14.3.0.12, V2312.0008, V2406.0005) or Tecnomatix Plant Simulation (V2302.0018, V2404.0007), and avoid opening untrusted WRL files from unverified sources.
V2302.0018 for V2302 branch; V2404.0007 for V2404 branch
- 1. Identify the current Tecnomatix Plant Simulation version from the About dialog or installation properties
- 2. If running V2302.x, upgrade to V2302.0018 or later
- 3. If running V2404.x, upgrade to V2404.0007 or later
- 4. Download the updated version from Siemens Industry Online Support (SIOS) or your authorized distribution channel
- 5. Install the upgrade following standard Siemens installation procedures
- 6. Verify the installed version matches the fixed release after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52567 — 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-52567 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