dbcve.org
Drawings SdkApplication · Opendesign

CVE-2022-28807

HIGH · 7.8 CVSS v3.1 Published 2022-07-17
Fix available
A fix is available. Upgrade to 2023.2 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 2023.2. An Out-of-Bounds Read vulnerability exists when rendering a .dwg file after it's opened in the recovery mode. 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 2023.2 contains an out-of-bounds read vulnerability triggered when rendering a .dwg file opened in recovery mode. An attacker can craft a malicious .dwg file that causes the SDK to read memory outside allocated buffers during recovery processing, leading to code execution in the context of the current process.

MitigationUpgrade to Drawings SDK 2023.2 or later. Until then, disable or avoid using recovery mode when opening untrusted .dwg files, and consider sandboxing applications using the 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:< 2023.2

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 the Drawings SDK version in use
    Locate the SDK version from the application's documentation, SDK headers, or by inspecting the installed ODA library files. Common locations include the SDK's release notes, version headers, or the binary file properties.
    Affected if The installed version is earlier than 2023.2 (for example, 2022.x, 2021.x, or earlier releases)
  2. Determine if recovery mode is enabled for .dwg file handling
    Review the application or integration code that uses the Drawings SDK to see if the recovery mode flag or option is set when opening .dwg files. Look for API calls that explicitly enable recovery processing.
    Affected if The application uses recovery mode when opening .dwg files (the API call typically includes a recovery or repair flag)
  3. Identify applications or components that process untrusted .dwg files
    Audit the environment for software that uses the ODA Drawings SDK to open .dwg files, particularly from external or untrusted sources. Check which applications handle these files and whether they invoke recovery mode.
    Affected if Applications process .dwg files from untrusted sources using recovery mode with a vulnerable SDK version
  4. Verify the SDK version matches vulnerable range
    Compare the identified SDK version number against the affected range: any version prior to 2023.2 is vulnerable if recovery mode is used.
    Affected if The SDK version is less than 2023.2 AND the application uses recovery mode when opening .dwg files

You are affected if your environment uses ODA Drawings SDK versions earlier than 2023.2 and any application or process opens .dwg files using the recovery mode feature.

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.2 or later
Fixed in 2023.2
Interim mitigation

Upgrade to Drawings SDK 2023.2 or later. Until then, disable or avoid using recovery mode when opening untrusted .dwg files, and consider sandboxing applications using the SDK.

Recommended fix High confidence

Drawings SDK 2023.2

  1. Obtain Drawings SDK version 2023.2 or later from the official Open Design Alliance website (www.opendesign.com)
  2. Replace the vulnerable SDK library file(s) in your project with the fixed version
  3. Rebuild your application to link against the updated SDK
  4. Test that the application correctly handles .dwg files, particularly those opened in recovery mode
  5. Deploy the rebuilt application with the fixed SDK
Caveat No breaking changes mentioned in the provided vulnerability description; upgrade to the next stable release

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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