CVE-2023-22354
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 · high confidenceDatakit CrossCadWare_x64.dll suffers from an out-of-bounds read vulnerability when parsing SLDPRT (SolidWorks part) files. The vulnerability occurs past the end of an allocated buffer during file parsing, potentially allowing disclosure of sensitive memory contents.
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.
-
Confirm Datakit Crosscadware is installedCheck for Datakit Crosscadware in installed programs list via Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or program files directoryAffected if Datakit Crosscadware software is present on the system
-
Identify installed Crosscadware versionLocate the CrossCadWare_x64.dll file (typically in the application bin folder) and check its file properties for version information, or query the software via its built-in about/help dialogAffected if The reported version is earlier than 2023.1 (e.g., 2022.x, 2021.x, etc.)
-
Verify vulnerable DLL existsSearch for CrossCadWare_x64.dll on the system using file explorer or command: dir /s C:\CrossCadWare_x64.dllAffected if CrossCadWare_x64.dll is found on the system at any version below 2023.1
-
Confirm SLDPRT file processing capabilityCheck if the software has SLDPRT import/conversion functionality enabled (typically visible in file open dialogs or import settings within the application)Affected if The software can open or convert SLDPRT (SolidWorks part) files
The system is affected if Datakit Crosscadware with CrossCadWare_x64.dll version earlier than 2023.1 is installed and has the ability to process SLDPRT 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
Avoid processing untrusted SLDPRT files with affected Datakit software; obtain and apply any available patches from the vendor.
2023.1
- Upgrade Datakit CrossCadWare to version 2023.1 or later
- Ensure the upgrade is applied to all systems running CrossCadWare_x64.dll
- After upgrading, re-parse any previously untrusted SLDPRT files to verify the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22354 — 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-22354 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