CVE-2022-28808
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 DWG files 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 confidenceAn out-of-bounds read vulnerability exists in Open Design Alliance Drawings SDK versions prior to 2023.3 when parsing DWG files specifically in recovery mode. The vulnerability allows a specially crafted malicious DWG file to trigger memory corruption that can lead to arbitrary code execution in the context of the process opening 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 versionLocate the ODA Drawings SDK DLL files (typically named OdDwg* or similar) in the application directory or system, then right-click to view Properties > Details and check the File Version. Alternatively, check the SDK header files or documentation shipped with the application.Affected if The reported version is earlier than 2023.3 (for example, 2022.x, 2021.x, or any version number less than 2023.3)
-
Determine if recovery mode is used for DWG filesReview the application logs, settings, or code that invokes the Drawings SDK. Look for function calls or parameters that enable DWG recovery mode, such asRecoveryMode(true) or similar API options when opening DWG files.Affected if The application or process opens DWG files using recovery mode enabled (this setting is often visible in file open options or debug traces)
-
Identify applications using vulnerable SDKSearch the system for executables or applications that bundle the ODA Drawings SDK DLLs. Use tools like Process Explorer or examine the application's dependencies to confirm it uses the Drawings SDK for DWG file handling.Affected if An application that handles DWG files is found using a version of the Drawings SDK prior to 2023.3 and has recovery mode available as a feature
You are affected if you have an application using Open Design Alliance Drawings SDK version lower than 2023.3 that opens DWG files in recovery mode.
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
Update Drawings SDK to version 2023.3 or later to obtain the patch for this vulnerability. Avoid opening untrusted or unknown DWG files in recovery mode until the update is applied.
Drawings SDK 2023.3
- 1. Obtain the Drawings SDK version 2023.3 or later from the official Open Design Alliance website (www.opendesign.com)
- 2. Review the SDK installation documentation provided by Open Design Alliance
- 3. Update your application to link against the updated Drawings SDK version 2023.3
- 4. Rebuild and test your application to ensure the updated SDK integrates properly
- 5. Verify that DWG file processing continues to function correctly in your application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28808 — 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-28808 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