CVE-2023-22846
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 has an out-of-bounds read vulnerability when parsing SLDPRT (SolidWorks part) files. The library reads 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.
-
Identify if Datakit Crosscadware is installedSearch for Crosscadware or CrossCadWare_x64.dll in installed programs, or check common installation directories such as C:\Program Files\Datakit or C:\Program Files (x86)\DatakitAffected if Datakit Crosscadware software is present on the system
-
Determine the installed Crosscadware versionCheck the program's version information: right-click the executable or DLL, select Properties, then Details, or use system inventory tools to query installed software versionsAffected if The installed version is lower than 2023.1 (for example, 2022.x, 2021.x, or earlier releases)
-
Locate the CrossCadWare_x64.dll fileSearch for CrossCadWare_x64.dll on the system using file search or review installation directoriesAffected if The DLL file exists and its version matches an affected Crosscadware release
-
Check if SLDPRT file processing is usedReview workflows or applications that use Datakit Crosscadware to determine if SolidWorks part files (.sldprt) are processed or importedAffected if The environment processes, imports, or converts SLDPRT files using the vulnerable library
A system is affected if Datakit Crosscadware is installed with a version lower than 2023.1 and processes SLDPRT files, as the out-of-bounds read vulnerability exists in CrossCadWare_x64.dll when parsing these 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
Apply vendor-supplied patches or updates to Datakit CrossCadWare. Until an official patch is available, implement file validation and restrict processing of untrusted SLDPRT files.
Crosscadware 2023.1
- 1. Identify the current version of Crosscadware installed in your environment
- 2. Download Crosscadware version 2023.1 or later from the official vendor source
- 3. Test the upgrade in a non-production environment first
- 4. Apply the upgrade to production systems following standard change management procedures
- 5. Verify the installation was successful and the version is correct
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22846 — 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-22846 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