CVE-2024-3299
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 · uneditedOut-Of-Bounds Write, Use of Uninitialized Resource and Use-After-Free vulnerabilities exist in the file reading procedure in eDrawings from Release SOLIDWORKS 2023 through Release SOLIDWORKS 2024. These vulnerabilities could allow an attacker to execute arbitrary code while opening a specially crafted SLDDRW or SLDPRT file. NOTE: this vulnerability was SPLIT from CVE-2024-1847.
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 confidenceThree memory corruption vulnerabilities (out-of-bounds write, use of uninitialized resource, use-after-free) exist in eDrawings' file reading procedure for parsing SLDDRW and SLDPRT files from SOLIDWORKS 2023-2024. A specially crafted file can trigger these flaws during parsing, leading to 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.
-
Identify if eDrawings or SOLIDWORKS is installedCheck the system for eDrawings or SOLIDWORKS installation directories. Common paths: C:\Program Files\SOLIDWORKS Corp\eDrawings or C:\Program Files\SOLIDWORKS Corp\SOLIDWORKSAffected if Neither eDrawings nor SOLIDWORKS is installed on the system
-
Determine the installed version of eDrawingsOpen eDrawings, go to Help > About eDrawings, or check the version in the application's executable properties (right-click eDrawings.exe > Properties > Details > File version)Affected if The version falls within the 2023 to 2024 range (e.g., 2023.x, 2024.x) and has not been patched to the vendor release
-
Determine the installed version of SOLIDWORKSCheck SOLIDWORKS version via Help > About SOLIDWORKS or examine the installation directory name which typically includes the version yearAffected if The installed SOLIDWORKS version is 2023 or 2024 and has not been patched to the vendor release
-
Verify if eDrawings is configured to handle SLDDRW or SLDPRT filesCheck file association settings in Windows: Right-click a .SLDDRW or .SLDPRT file > Open with > Choose default program, or inspect eDrawings file association settings within the applicationAffected if eDrawings is set as the default handler for SLDDRW or SLDPRT files and the version is within the affected range
The system is affected if eDrawings or SOLIDWORKS version 2023 or 2024 is installed and configured to parse SLDDRW or SLDPRT files without vendor patches applied.
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 dataUpdate eDrawings/SOLIDWORKS to the vendor's patched release; avoid opening untrusted SLDDRW or SLDPRT files until patched.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3299 — 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-3299 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