dbcve.org
Drawings SdkApplication · Opendesign

CVE-2023-5179

HIGH · 7.8 CVSS v3.1 Published 2023-11-07
Fix available
A fix is available. Upgrade to 2024.10 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.10. A corrupted value for the start of MiniFat sector in a crafted DGN file leads to an out-of-bounds read. This can allow attackers to cause a crash, potentially enabling a denial-of-service attack (Crash, Exit, or Restart) or possible code execution.

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

An out-of-bounds read vulnerability exists in Open Design Alliance Drawings SDK versions before 2024.10. The vulnerability is triggered by a crafted DGN file containing a corrupted value for the start of the MiniFat sector, causing the parser to read memory outside intended bounds, potentially leading to crash, DoS, or code execution.

MitigationUpdate to Drawings SDK version 2024.10 or later to receive the patch. Until then, implement input validation to detect and reject DGN files with anomalous MiniFat sector values.

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.10

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 ODA Drawings SDK is installed
    Search for ODA SDK DLLs or libraries on the system. Common file names include OdDgnDb.dll, OdDgnModule.dll, or other Od*.dll files in application directories or system paths. Use file system search or check application dependency lists.
    Affected if The ODA Drawings SDK or applications using it are found on the system
  2. Determine the installed SDK version
    Right-click on the ODA SDK DLL files (such as OdDgnDb.dll) and select Properties, then inspect the 'File version' or 'Product version' field in the Details tab. Alternatively, check the application's documentation or release notes for the bundled ODA SDK version.
    Affected if The version is lower than 2024.10 (for example, 2024.9, 2024.8, or earlier)
  3. Check if DGN file processing is in use
    Review the application configuration or search for DGN-related import/export settings. Look for DGN file handlers or converters in the application, or monitor for .dgn file operations.
    Affected if The application is configured to import, export, or otherwise process DGN files
  4. Audit DGN files in the environment
    Search for .dgn files on the system using file search tools, particularly in directories where design files are stored or processed.
    Affected if DGN files exist and are processed by an application using a vulnerable version of the ODA Drawings SDK

You are affected if the Open Design Alliance Drawings SDK version is below 2024.10 and your application processes DGN files.

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.10 or later
Fixed in 2024.10
Interim mitigation

Update to Drawings SDK version 2024.10 or later to receive the patch. Until then, implement input validation to detect and reject DGN files with anomalous MiniFat sector values.

Recommended fix High confidence

2024.10

  1. Obtain Drawings SDK version 2024.10 or later from www.opendesign.com
  2. Update the Open Design Alliance Drawings SDK dependency in your project to version 2024.10
  3. Rebuild your application with the updated SDK
  4. Test that DGN file parsing still functions correctly with the updated SDK

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

Fix this in Drawings Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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