CVE-2018-18223
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 · uneditedOpen Design Alliance Drawings SDK 2019Update1 has a vulnerability during the reading of malformed files, allowing attackers to obtain sensitive information from process memory or cause a crash.
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 · moderate confidenceThe Open Design Alliance Drawings SDK 2019 Update 1 contains a vulnerability when parsing malformed DWG/DXF files. Attackers can exploit this to read sensitive information from process memory (indicating an out-of-bounds read vulnerability) or cause a denial of service via crash. The CVSS 8.1 suggests remote exploitability with low complexity.
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= 2019= 8.5.3= 8.5.4CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 ODA Drawings SDK installationCheck for presence of ODA Drawings SDK libraries or applications that use them. Look for files named 'ODA' or 'OpenDesign' in program directories, or check application dependencies for ODA components.Affected if ODA Drawings SDK version 2019 is installed and actively used for DWG/DXF file processing
-
Identify Oracle Outside In Technology installationCheck for Oracle Outside In Technology installation directories (commonly under Oracle or product-specific paths). Query installed software for 'Outside In' versions 8.5.3 or 8.5.4.Affected if Oracle Outside In Technology versions 8.5.3 or 8.5.4 are installed
-
Determine DWG/DXF processing usageIdentify applications or services that accept or process DWG or DXF file input. Review file upload handlers, document conversion workflows, or CAD-related processes.Affected if Systems accept and process DWG or DXF files using the affected SDK versions
-
Assess exposure to untrusted filesReview whether DWG/DXF files from external or untrusted sources are processed. Check file upload mechanisms, email attachments handling, or document import features.Affected if The system processes DWG/DXF files from untrusted or external sources without strict validation
Your environment is affected if you have ODA Drawings SDK 2019 or Oracle Outside In Technology 8.5.3/8.5.4 installed and these components process DWG/DXF files, particularly 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.
From vendor dataUpdate to the patched version of ODA Drawings SDK when available, implement strict file validation before processing, and run the SDK in sandboxed environments to limit exposure to malformed file attacks.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18223 — 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-2018-18223 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