CVE-2023-2762
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 Use-After-Free vulnerability in SLDPRT file reading procedure exists in SOLIDWORKS Desktop from Release SOLIDWORKS 2021 through Release SOLIDWORKS 2023. This vulnerability could allow an attacker to execute arbitrary code while opening a specially crafted SLDPRT file.
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 Use-After-Free vulnerability exists in the SLDPRT file parsing component of SOLIDWORKS Desktop versions 2021-2023. When opening a specially crafted SLDPRT file, the application improperly manages memory allocation/deallocation, freeing a memory buffer while retaining a pointer to it. This allows an attacker to control the freed memory through a subsequent allocation, potentially achieving arbitrary code execution.
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>= 2021, <= 2023CVSS 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 SOLIDWORKS Desktop installationCheck for SOLIDWORKS installation by looking in Program Files\SOLIDWORKS Corp\ or checking the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\SOLIDWORKS or HKEY_CURRENT_USER\SOFTWARE\SOLIDWORKSAffected if SOLIDWORKS Desktop is not found on the system, the system is not affected by this CVE
-
Identify installed SOLIDWORKS versionOpen SOLIDWORKS and go to Help > About SOLIDWORKS, or check the version in the Windows Registry under the SOLIDWORKS installation key (key name typically contains the version year such as 2021, 2022, or 2023)Affected if The installed version falls within the range 2021 through 2023 (inclusive), the system falls within the affected version range
-
Verify SLDPRT file handling is activeConfirm that SLDPRT files can be opened in the installed SOLIDWORKS version - attempt to open a known SLDPRT file or check file association settings for .SLDPRT extensionAffected if SLDPRT files can be opened and parsed by the application, the vulnerable parsing component is accessible and the system could be exploited by opening malicious files
-
Check for untrusted file processing riskReview whether the system environment allows opening SLDPRT files from external or untrusted sources, such as email attachments, downloaded files, or network sharesAffected if Users can open SLDPRT files from untrusted sources directly in SOLIDWORKS, the exploitation vector is present and the system is at risk
The environment is affected if SOLIDWORKS Desktop versions 2021, 2022, or 2023 are installed and SLDPRT files can be opened, enabling exploitation through specially crafted 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 · scopedApply vendor-provided security patches from SOLIDWORKS for versions 2021 through 2023. Until patches are available, refrain from opening SLDPRT files from untrusted sources and consider using application sandboxing or email gateway filtering for SLDPRT attachments.
SOLIDWORKS 2024 or later
- Identify the current installed SOLIDWORKS version by opening SOLIDWORKS and going to Help > About SOLIDWORKS
- Navigate to the official 3DS (Dassault Systèmes) support portal at www.3ds.com to obtain the latest SOLIDWORKS version
- Download and install SOLIDWORKS 2024 or later version, as this vulnerability affects versions 2021 through 2023
- Ensure all users who open SLDPRT files are informed not to open files from untrusted sources until the upgrade is complete
- After upgrading, verify the version by checking Help > About SOLIDWORKS to confirm the installation was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2762 — 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-2762 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