CVE-2021-43390
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 · uneditedAn Out-of-Bounds Write vulnerability exists when reading a DGN file using Open Design Alliance Drawings SDK before 2022.11. The specific issue exists within the parsing of DGN files. Crafted data in a DGN file and lack of proper validation of input data can trigger a write operation past the end of an allocated 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 confidenceAn out-of-bounds write vulnerability exists in Open Design Alliance Drawings SDK versions prior to 2022.11 when parsing DGN files. The vulnerability stems from insufficient validation of input data during DGN file parsing, allowing a crafted DGN file to trigger a write operation beyond the bounds of an allocated buffer, potentially leading to arbitrary code execution in the current process context.
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< 2022.11CVSS 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.
-
Identify if ODA Drawings SDK is installedSearch for files named OdDbDgnLoader.dll, OdDgnModule.dll, or other ODA SDK DLLs in application directories, or check product installation folders for 'Open Design Alliance' or 'ODA' software components.Affected if The SDK DLLs are present in the environment.
-
Determine the installed SDK versionRight-click on the ODA SDK DLL (e.g., OdDbDgnLoader.dll) and view Properties > Details to find the File Version, or check the product's about/version information if installed as a full application.Affected if The version is lower than 2022.11 or the version cannot be determined (indicating an old release).
-
Identify applications using the ODA Drawings SDKReview application logs, dependencies, or software inventory to find which applications or services link against ODA SDK libraries.Affected if Any application or service uses the ODA Drawings SDK for file processing.
-
Check if DGN file processing is enabledReview application configuration files, registry keys, or feature toggles for DGN import/export functionality. Look for DGN-related modules, plugins, or file handlers.Affected if DGN file parsing or conversion features are enabled or used.
-
Determine source of DGN filesAudit file upload directories, import workflows, or document management systems that accept DGN files to identify if untrusted DGN files can be processed.Affected if The system processes DGN files from external or untrusted sources.
The environment is affected if ODA Drawings SDK version lower than 2022.11 is installed AND DGN file parsing is enabled, particularly when processing files from external or untrusted sources.
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 · scoped2022.11
Update Drawings SDK to version 2022.11 or later to obtain the vendor patch. Until then, avoid processing untrusted DGN files and implement file validation routines.
2022.11
- Obtain Open Design Alliance Drawings SDK version 2022.11 or later from www.opendesign.com
- Replace the vulnerable SDK version in your project dependencies or build configuration
- Rebuild and recompile your application with the updated SDK
- Verify that DGN file parsing functionality works correctly with the new SDK version
- Test the application with various DGN files to ensure the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43390 — 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-2021-43390 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