CVE-2022-28809
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 issue was discovered in Open Design Alliance Drawings SDK before 2023.3. An Out-of-Bounds Read vulnerability exists when reading a DWG file with an invalid vertex number in a 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 confidenceThe Open Design Alliance Drawings SDK before version 2023.3 contains an out-of-bounds read vulnerability when parsing DWG files with an invalid vertex number while in recovery mode. This memory corruption issue can be triggered by a specially crafted DWG file, potentially allowing an attacker to achieve code execution in the context of the process handling the file.
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< 2023.3CVSS 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 Drawings SDK installationSearch for ODA Drawings SDK DLLs or libraries (typically named odaws, odax, or similar) in application directories or system paths, and check file properties for version informationAffected if The SDK version is found to be below 2023.3
-
Determine SDK version programmaticallyIf using an application that links against the ODA SDK, inspect the loaded DLL/library version using tools like dumpbin, Dependencies, or by querying the file version resource of the SDK binaryAffected if The reported version is less than 2023.3 or version information is missing/unknown
-
Identify applications using the Drawings SDKReview application dependencies or examine process memory during DWG file handling to identify if the ODA Drawings SDK is in useAffected if An application loads and uses the ODA Drawings SDK for DWG processing
-
Check if DWG recovery mode is in useReview application settings, logs, or configuration files for options related to DWG recovery mode, file repair, or file salvage features when processing DWG filesAffected if Recovery mode or file recovery options are enabled for DWG file processing
-
Verify DWG file processing activityMonitor or audit processes that handle DWG files, particularly those involving file recovery or repair operations, to confirm the vulnerable code path is reachableAffected if The application processes untrusted DWG files with recovery mode enabled
You are affected if the ODA Drawings SDK version is below 2023.3 AND your application uses recovery mode to parse DWG files from 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 · scoped2023.3
Upgrade Drawings SDK to version 2023.3 or later to obtain the security patch. Additionally, implement input validation and avoid processing untrusted DWG files in recovery mode until the update is applied.
Drawings SDK 2023.3
- Identify the current version of Open Design Alliance Drawings SDK in use by checking project dependencies or SDK version
- Upgrade to Drawings SDK version 2023.3 or later from www.opendesign.com
- Rebuild and recompile any applications that link to or depend on the Drawings SDK library
- Verify that applications function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28809 — 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-2022-28809 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