CVE-2023-27385
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 vulnerability exists in CX-Drive All models all versions. By having a user open a specially crafted SDD file, arbitrary code may be executed and/or information may be disclosed.
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 confidenceA heap-based buffer overflow vulnerability exists in Omron CX-Drive (all models, all versions). The flaw is triggered when a user opens a specially crafted malicious SDD file, allowing attackers to achieve arbitrary code execution or disclose sensitive information.
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<= 3.01CVSS 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.
-
Locate CX-Drive installation directorySearch the system for 'CX-Drive' folder, typically found in Program Files (x86)\Omron or C:\Program Files\Omron. Check both paths for the CX-Drive application.Affected if CX-Drive software is not found on the system (not affected)
-
Identify installed CX-Drive versionRight-click the CX-Drive executable (usually named CX-Drive.exe or similar), select Properties, and check the Details tab for the File Version or Product Version.Affected if Version is 3.01 or lower (likely affected)
-
Verify version via Windows Programs listOpen Windows Control Panel > Programs and Features, locate 'Omron CX-Drive' in the list, and note the version column.Affected if Version displays as 3.01 or below (affected)
-
Confirm SDD file type associationCheck if .sdd files are associated with CX-Drive by right-clicking any .sdd file in File Explorer, selecting Properties, and viewing the 'Opens with' section.Affected if SDD files open with CX-Drive (vulnerable feature is active)
-
Inspect recent SDD file activityReview the system's recent documents or check the CX-Drive recent files list within the application to see if SDD files have been opened.Affected if SDD files have been opened using CX-Drive (potential exploitation vector present)
User is affected if Omron CX-Drive version 3.01 or lower is installed and SDD files are handled by this software.
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 when released; until then, avoid opening SDD files from untrusted sources and implement file sandboxing or email gateway filtering for SDD attachments.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27385 — 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-27385 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