CVE-2023-30986
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 Solid Edge SE2023 (All versions < V223.0 Update 3), Solid Edge SE2023 (All versions < V223.0 Update 2). Affected applications contain a memory corruption vulnerability while parsing specially crafted STP files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-19561)
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 confidenceMemory corruption vulnerability in Solid Edge SE2023 when parsing specially crafted STP (STEP) files. The vulnerability allows arbitrary code execution in the context of the current process due to improper handling of malicious STP file data during parsing.
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 dataall versions= update_0001CVSS 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 Solid Edge SE2023 version and update levelOpen Solid Edge SE2023 and navigate to Help > About Solid Edge to display the installed version and update level (such as update_0001, update_0002, or later)Affected if The displayed version is Solid Edge SE2023 with update level update_0001 or earlier (updates after update_0001 contain the fix)
-
Confirm STP file import capability is availableAttempt to open or import a standard STP/STEP file using File > Open or the application import functionality to verify the STP parser module is present and operationalAffected if The STP file import feature is accessible and functional in the installed version
-
Review recent document history for STP filesCheck the application recent files list or Windows jump lists for any recently opened STP files, or examine file system locations where STP files have been saved or downloadedAffected if STP files from any source have been opened or parsed in the application
Your environment is affected if Solid Edge SE2023 with update_0001 or earlier is installed and the STP file parsing feature has been used to process any STP 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 · scopedUpdate Solid Edge SE2023 to V223.0 Update 3 or later. Avoid opening untrusted STP files from unknown or untrusted sources until the patch is applied.
V223.0 Update 3 or later
- 1. Identify current Solid Edge SE2023 version by opening the application and checking Help > About Solid Edge
- 2. If version is earlier than V223.0 Update 3, obtain the fixed version from Siemens official support portal or update mechanism
- 3. Download and install Solid Edge V223.0 Update 3 or later from Siemens support channels
- 4. After upgrade, verify the version reflects V223.0 Update 3 or newer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30986 — 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-2023-30986 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