CVE-2023-22295
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 · uneditedDatakit CrossCadWare_x64.dll contains an out of bounds read past the end of an allocated buffer while parsing a specially crafted SLDPRT file. This vulnerability could allow an attacker to disclose sensitive information.
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 · moderate confidenceDatakit CrossCadWare_x64.dll suffers from an out-of-bounds read vulnerability when parsing SLDPRT (SolidWorks part) files. The vulnerability allows reading past the end of an allocated buffer, potentially exposing sensitive memory contents to an attacker who provides a specially crafted file.
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< 2023.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Locate the CrossCadWare_x64.dll fileSearch the system for CrossCadWare_x64.dll using file search or command: `Get-ChildItem -Path C:\ -Recurse -Filter CrossCadWare_x64.dll -ErrorAction SilentlyContinue` on Windows, or `find / -name CrossCadWare_x64.dll 2>/dev/null` on Linux/MacAffected if The DLL file exists on the system, indicating Datakit Crosscadware is installed
-
Identify the installed Datakit Crosscadware versionCheck the file properties of the DLL (right-click > Properties > Details) or check the installed program version in Add/Remove Programs. Look for version information in the product name or the DLL metadataAffected if The version shown is earlier than 2023.1 (for example, 2022.x, 2021.x, etc.)
-
Verify SLDPRT file parsing capabilityExamine the application logs or configuration to determine if SLDPRT (SolidWorks part) file parsing is enabled or commonly used. Check if any installed applications integrate Crosscadware for CAD file conversionAffected if The software is configured to process SLDPRT files, as the vulnerability triggers specifically when parsing these files
-
Review applications using the libraryIdentify which applications on the system depend on or load CrossCadWare_x64.dll. Check for CAD conversion tools, data exchange platforms, or import/export functionality that may invoke this libraryAffected if Applications that load this DLL are used to open files from untrusted sources
The environment is affected if Datakit Crosscadware version lower than 2023.1 is installed AND the library is used to parse SLDPRT files from any source, including untrusted 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 · scoped2023.1
Update to the patched version of Datakit CrossCadWare when available. Until then, avoid opening untrusted SLDPRT files in applications that use this library.
Crosscadware 2023.1 or later
- 1. Identify the current version of Crosscadware installed in your environment
- 2. Navigate to the official Datakit software download page or contact your software vendor for the latest version
- 3. Download Crosscadware version 2023.1 or later
- 4. Before upgrading, backup any existing Crosscadware installations and associated data
- 5. Uninstall or remove the older vulnerable version of Crosscadware
- 6. Install the new version 2023.1 or later
- 7. Verify the installation completed successfully
- 8. Test that SLDPRT file parsing functionality works correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22295 — 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-22295 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