CVE-2024-1848
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 · uneditedHeap-based Buffer Overflow, Memory Corruption, Out-Of-Bounds Read, Out-Of-Bounds Write, Stack-based Buffer Overflow, Type Confusion, Uninitialized Variable, Use-After-Free vulnerabilities exist in the file reading procedure in SOLIDWORKS Desktop on Release SOLIDWORKS 2024. These vulnerabilities could allow an attacker to execute arbitrary code while opening a specially crafted CATPART, DWG, DXF, IPT, JT, SAT, SLDDRW, SLDPRT, STL, STP, X_B or X_T 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 confidenceMultiple memory corruption vulnerabilities (heap/stack buffer overflows, out-of-bounds read/write, use-after-free, type confusion, uninitialized variables) exist in SOLIDWORKS 2024's file parsing for CATPART, DWG, DXF, IPT, JT, SAT, SLDDRW, SLDPRT, STL, STP, X_B, and X_T files. Opening a specially crafted file can trigger these issues, potentially allowing arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 SOLIDWORKS 2024 is installedCheck installed programs in Windows Control Panel or query the registry under HKLM:\SOFTWARE\SolidWorks, or inspect the installation directory typically at C:\Program Files\SOLIDWORKS Corp\SOLIDWORKSAffected if SOLIDWORKS 2024 is present on the system without the vendor patch applied
-
Confirm the exact version of SOLIDWORKS 2024Open SOLIDWORKS and navigate to Help > About SOLIDWORKS to view the version number, or right-click on SldWorks.exe in the installation folder and view Properties > Details for the File VersionAffected if The installed version falls within the SOLIDWORKS 2024 release line and has not been patched by the vendor
-
Identify if affected file types are processedUse File Explorer or PowerShell (Get-ChildItem -Recurse) to search for files with extensions CATPART, DWG, DXF, IPT, JT, SAT, SLDDRW, SLDPRT, STL, STP, X_B, or X_T on systems running SOLIDWORKS or in directories that users sync to SOLIDWORKSAffected if The environment contains any of these file types that users open with SOLIDWORKS 2024
-
Assess file source trust postureReview Windows Event Viewer logs, endpoint detection logs, or email/DLP logs to see if SOLIDWORKS users receive or open files from external sources such as email attachments, web downloads, or external removable mediaAffected if Users open files from untrusted or external sources in SOLIDWORKS 2024 without prior malware scanning
The environment is vulnerable if SOLIDWORKS 2024 is installed and users process any of the affected file types (CATPART, DWG, DXF, IPT, JT, SAT, SLDDRW, SLDPRT, STL, STP, X_B, X_T) from untrusted sources, as the vulnerability is triggered during file parsing.
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.
From vendor dataApply the vendor patch from Dassault Systèmes when available. Until then, implement compensating controls: restrict file opening permissions, sandbox SOLIDWORKS applications, scan files with endpoint protection before opening, and train users to only open files from trusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1848 — 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-1848 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