CVE-2023-49129
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 10). The affected applications contain a stack overflow vulnerability while parsing specially crafted PAR 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 Solid Edge SE2023 (versions prior to V223.0 Update 10) when parsing specially crafted PAR files. An attacker can exploit this 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< 223.0= 223.0CVSS 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 is installedCheck the Windows registry under HKLM\SOFTWARE\Siemens\Solid Edge\Version or look for the program in C:\Program Files\Siemens\Solid Edge SE2023Affected if Solid Edge SE2023 is present on the system
-
Determine the installed Solid Edge versionRun the executable with version flag, or check registry value at HKLM\SOFTWARE\Siemens\Solid Edge\Version\Current (the version string typically appears as a build number like 223.0.xxxx)Affected if The version cannot be determined or is earlier than V223.0 Update 10
-
Compare version against affected rangeCompare your installed build number against the affected versions: any build prior to V223.0 Update 10, including version 223.0 itself, is vulnerableAffected if Installed version is less than V223.0 Update 10 or exactly equals 223.0
-
Confirm PAR file parsing is accessibleVerify that the Solid Edge application can be launched and that users have the ability to open PAR (parametric) files through the applicationAffected if Users can launch Solid Edge and access the PAR file open functionality
If Solid Edge SE2023 is installed with a version prior to V223.0 Update 10 (including version 223.0), the environment is vulnerable when users can open PAR 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 · scoped223.0
Upgrade Solid Edge to V223.0 Update 10 or later to remediate this vulnerability. Avoid opening untrusted PAR files from unknown or unverified sources until the patch is applied.
V223.0 Update 10
- 1. Identify the current installed version of Solid Edge SE2023
- 2. Verify if the installed version is earlier than V223.0 Update 10
- 3. Obtain and install Solid Edge SE2023 V223.0 Update 10 or later from official Siemens channels
- 4. Verify the installed version reflects the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49129 — 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-49129 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