CVE-2024-52572
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 a stack based overflow vulnerability while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-24486)
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 confidenceStack-based buffer overflow vulnerability in Teamcenter Visualization and Tecnomatix Plant Simulation when parsing specially crafted WRL (VRML) files. The overflow occurs during WRL file parsing and can be exploited 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< 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 if Tecnomatix Plant Simulation is installedCheck for the presence of Siemens Tecnomatix Plant Simulation in the system registry (HKLM\SOFTWARE\Siemens\Tecnomatix\PlantSimulation) or locate the installation directory (typically under C:\Program Files\Siemens\Tecnomatix Plant Simulation)Affected if The software is installed and its version falls within the affected ranges
-
Determine the installed version of Tecnomatix Plant SimulationLocate the version information in the registry key or check the About/Version dialog within the application. Compare the version number to the affected ranges: < 2302.0018 or >= 2404.0 and < 2404.0007Affected if The installed version is less than 2302.0018, or is 2404.0 through 2404.0006 inclusive
-
Verify if WRL file parsing functionality existsCheck if the application has the capability to import or open WRL (VRML) files. This may be evidenced by WRL file type associations, import filters, or by attempting to locate the WRL import module within the installation directoryAffected if WRL file import capability is present and the version is within the affected ranges listed above
-
Check for recent WRL file processing activityReview application logs, recent file access timestamps, or audit logs for any WRL file imports that may have occurred, particularly with files from untrusted sourcesAffected if WRL files have been opened or imported using the affected software versions
A user is affected if Tecnomatix Plant Simulation is installed with a version less than 2302.0018, or between 2404.0 and 2404.0006 inclusive, and the application can parse 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
Apply vendor-supplied patches to reach the fixed versions: Teamcenter Visualization V14.2.0.14+, V14.3.0.12+, V2312.0008+, V2406.0005+ and Tecnomatix Plant Simulation V2302.0018+, V2404.0007+. Avoid opening untrusted WRL files until patches are applied.
Tecnomatix Plant Simulation V2302.0018 or V2404.0007 (depending on your major version line)
- 1. Identify the currently installed Tecnomatix Plant Simulation version from the About or system information menu
- 2. For Tecnomatix Plant Simulation V2302 users: Upgrade to version V2302.0018 or later
- 3. For Tecnomatix Plant Simulation V2404 users: Upgrade to version V2404.0007 or later
- 4. Verify the upgrade was successful by checking the installed version matches or exceeds the fixed release
- 5. As a general precaution, avoid opening untrusted WRL files from unknown or untrusted sources until the patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52572 — 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-52572 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