CVE-2023-39183
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 7). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted PSM 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 confidenceSolid Edge SE2023 contains an out-of-bounds read vulnerability in PSM file parsing that reads past the end of an allocated structure. Successful exploitation allows arbitrary 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< se2023= se2023CVSS 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.
-
Confirm Solid Edge SE2023 installationCheck for Solid Edge SE2023 in the installed programs list (Windows Control Panel > Programs and Features) or look for the installation directory typically under C:\Program Files\Siemens\Solid Edge SE2023Affected if Solid Edge SE2023 is installed on the system
-
Identify installed Solid Edge version numberOpen Solid Edge SE2023 and navigate to Help > About Solid Edge, or check the version in the Windows registry under HKLM\SOFTWARE\Siemens\Solid Edge\CurrentVersionAffected if The displayed version matches or falls within the SE2023 release family
-
Compare version to affected rangeLocate the full version string (such as V223.0.x) and compare it against the vulnerable version range. The vulnerability affects SE2023 versions prior to V223.0 Update 7Affected if The installed version is SE2023 and is earlier than V223.0 Update 7, or if the exact version cannot be determined but the product is confirmed as SE2023
-
Determine PSM file usage contextIdentify if the system processes or opens PSM (Part Standard Mesh) files, which are native Solid Edge part files. Check recent file access or look for PSM file associations in the Solid Edge installationAffected if PSM files are routinely opened or processed in the current environment, as this is the attack vector for exploiting the vulnerability
A user is affected if Solid Edge SE2023 is installed with a version prior to V223.0 Update 7 and the system processes or opens PSM 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 version V223.0 Update 7 or later to patch the vulnerability.
V223.0 Update 7
- Upgrade Solid Edge SE2023 to version V223.0 Update 7 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39183 — 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-39183 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