Drawings SdkApplication · Opendesign

CVE-2023-22669

HIGH · 7.8 CVSS v3.1 Published 2023-04-15
Fix available
A fix is available. Upgrade to 2023.6 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Parsing of DWG files in Open Design Alliance Drawings SDK before 2023.6 lacks proper validation of the length of user-supplied XRecord data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process.

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 confidence

A heap-based buffer overflow vulnerability exists in Open Design Alliance Drawings SDK versions prior to 2023.6 when parsing DWG files. The SDK fails to validate the length of user-supplied XRecord data before copying it to a fixed-length heap buffer, allowing an attacker to achieve arbitrary code execution via a specially crafted DWG file.

MitigationUpdate Drawings SDK to version 2023.6 or later which contains the proper bounds-checking validation for XRecord data length.

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
Drawings SdkApplication
Affected:< 2023.6

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate ODA Drawings SDK installation
    Search for files named 'Oda' or 'ODA' or 'Opendesign' in common library directories, or check application dependencies that may bundle the SDK. Inspect the application's binary or manifest files for references to 'ODA', 'Drawings', or 'OpDesign'.
    Affected if The SDK is present in the environment
  2. Determine SDK version
    Check version information in the SDK binaries, associated version files, or the application's metadata that references the ODA Drawings SDK version.
    Affected if Version is missing from metadata or shows a version number less than 2023.6
  3. Verify DWG parsing is enabled
    Determine if the application or system uses DWG file parsing functionality from the ODA Drawings SDK. This may be evident from file type handlers, import/export features, or CAD-related functionality.
    Affected if DWG file parsing feature is actively used or available in the environment
  4. Compare against affected range
    If a version number is obtained, compare it to the affected range: versions prior to 2023.6 are vulnerable.
    Affected if Installed version is below 2023.6 and DWG parsing is in use

Environment is affected if ODA Drawings SDK version below 2023.6 is present and DWG file parsing functionality is enabled or available.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2023.6 or later
Fixed in 2023.6
Interim mitigation

Update Drawings SDK to version 2023.6 or later which contains the proper bounds-checking validation for XRecord data length.

Recommended fix High confidence

Drawings SDK 2023.6

  1. Obtain the latest version of Open Design Alliance Drawings SDK (2023.6 or later) from the official vendor website at www.opendesign.com
  2. Upgrade your installation to Drawings SDK version 2023.6 or newer
  3. Verify that the installed version is 2023.6 or later by checking the SDK version information
  4. Rebuild and redeploy any applications that use the Drawings SDK to ensure they link against the updated library

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drawings Sdk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22669 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22669 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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