dbcve.org
Drawings SdkApplication · Opendesign

CVE-2023-5180

HIGH · 7.8 CVSS v3.1 Published 2023-12-26
Fix available
A fix is available. Upgrade to 2024.12 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
An issue was discovered in Open Design Alliance Drawings SDK before 2024.12. A corrupted value of number of sectors used by the Fat structure in a crafted DGN file leads to an out-of-bounds write. 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

Open Design Alliance Drawings SDK before version 2024.12 contains an out-of-bounds write vulnerability triggered by a crafted DGN file with a corrupted FAT sector count value. This memory corruption allows an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate Drawings SDK to version 2024.12 or later to patch the out-of-bounds write vulnerability in DGN file parsing. Until updated, avoid opening untrusted DGN files with applications using this SDK.

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:< 2024.12

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. Identify if OpenDesign Drawings SDK is installed
    Search for ODA SDK files on the system. Common install locations include C:\Program Files\ODA\ or C:\Program Files (x86)\ODA\ on Windows, or /usr/local/oda/ or /opt/oda/ on Linux. Look for directories named "Drawings SDK" or containing "oda", "dgn", or "dwg" related files.
    Affected if The OpenDesign Drawings SDK is present on the system
  2. Determine the installed Drawings SDK version
    Check for version information in SDK files. Common files to inspect: version.h, about.txt, or the main DLL/SO libraries. The version may be embedded in file properties or a dedicated version.txt file in the SDK root directory.
    Affected if The installed version is lower than 2024.12 (for example, 2024.11, 2024.1, 2023.x, or earlier)
  3. Identify applications using the Drawings SDK
    Review installed applications that handle DGN files. Check application dependencies or manifests for ODA SDK references. On Windows, examine loaded DLLs for "oda" or "OpDesign" libraries when running DGN-processing applications.
    Affected if An application that processes DGN files is using an affected version of the ODA Drawings SDK
  4. Verify DGN file processing is enabled
    Determine if the vulnerable feature (DGN file parsing) is actively used. Review application settings or configurations for DGN import/export functionality. Check if users have opened or can open DGN files through the application.
    Affected if DGN file parsing is enabled and the application can load DGN files from external sources

The environment is affected if OpenDesign Drawings SDK version below 2024.12 is installed and applications using it can process DGN files, allowing a crafted DGN file with corrupted FAT sector count to trigger the out-of-bounds write.

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 2024.12 or later
Fixed in 2024.12
Interim mitigation

Update Drawings SDK to version 2024.12 or later to patch the out-of-bounds write vulnerability in DGN file parsing. Until updated, avoid opening untrusted DGN files with applications using this SDK.

Recommended fix High confidence

2024.12

  1. Obtain Drawings SDK version 2024.12 or later from the official Open Design Alliance source (www.opendesign.com)
  2. Replace the vulnerable version of the Drawings SDK in your application with version 2024.12 or later
  3. Rebuild your application with the updated SDK
  4. Redeploy the rebuilt application to ensure the vulnerability is remediated

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

Fix this in Drawings Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-5180 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