dbcve.org
Drawings Software Development KitApplication · Opendesign

CVE-2021-43391

HIGH · 7.8 CVSS v3.1 Published 2021-11-14
Fix available
A fix is available. Upgrade to 2022.11 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 Out-of-Bounds Read vulnerability exists when reading a DXF file using Open Design Alliance Drawings SDK before 2022.11. The specific issue exists within the parsing of DXF files. Crafted data in a DXF file (an invalid dash counter in line types) can trigger a read 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 confidence

An out-of-bounds read vulnerability exists in Open Design Alliance Drawings SDK versions prior to 2022.11 when parsing DXF files. The specific issue occurs during parsing of DXF line types where an invalid dash counter causes the parser to read beyond the boundaries of an allocated buffer. This memory access violation can potentially be exploited to achieve code execution in the context of the current process.

MitigationUpgrade to ODA Drawings SDK version 2022.11 or later to obtain the patch. Additionally, implement input validation on DXF files before processing and consider sandboxing file parsing operations to limit the impact of exploitation.

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 Software Development KitApplication
Affected:< 2022.11

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 in use
    Search for files named OdDb.dll, OdDxf.dll, or other ODA SDK DLLs in your application directory and system paths. Check application dependencies or manifests that reference Open Design Alliance libraries.
    Affected if The ODA Drawings SDK DLLs are present in the environment
  2. Determine the installed SDK version
    Locate the ODA SDK DLL files and check their version properties (right-click > Properties > Details > File Version). Alternatively, check the product version information embedded in the SDK libraries or check your application's dependency documentation.
    Affected if The version is earlier than 2022.11 (e.g., 2022.10, 2022, 2021.x, etc.)
  3. Verify DXF file processing is enabled
    Examine application configuration files or settings that control file format support. Look for options enabling DXF import, read, or parsing functionality.
    Affected if DXF file processing is enabled and the application can load DXF files
  4. Confirm line type parsing is active
    Review application logs or debug output during DXF file loading. Check if line type entities (LTYPE) in DXF files are being processed by the SDK.
    Affected if Line type parsing from DXF files is performed by the application
  5. Check for DXF file input handling
    Identify how DXF files enter the system: user uploads, file import features, automated processing pipelines, or API endpoints that accept DXF input.
    Affected if The application accepts and processes DXF files from external sources

You are affected if the ODA Drawings SDK version is earlier than 2022.11 and your application parses DXF files with line type data enabled.

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

Upgrade to ODA Drawings SDK version 2022.11 or later to obtain the patch. Additionally, implement input validation on DXF files before processing and consider sandboxing file parsing operations to limit the impact of exploitation.

Recommended fix High confidence

Drawings SDK version 2022.11

  1. 1. Identify all deployed instances of Open Design Alliance Drawings SDK in your environment
  2. 2. Verify the currently installed version of the Drawings SDK
  3. 3. Download Drawings SDK version 2022.11 or later from the official Open Design Alliance website (www.opendesign.com)
  4. 4. Test the new SDK version in a staging environment to ensure compatibility with your application
  5. 5. Deploy the upgraded SDK to production environments
  6. 6. Ensure DXF file processing continues to function correctly after the upgrade

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

Fix this in Drawings Software Development Kit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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