CVE-2021-38107
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 · uneditedCdrCore.dll in Corel DrawStandard 2020 22.0.0.474 is affected by an Out-of-bounds Read vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to access unauthorized system memory in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious CDR file.
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 confidenceCdrCore.dll in Corel Draw Standard 2020 22.0.0.474 contains an out-of-bounds read vulnerability when parsing specially crafted CDR files. An unauthenticated attacker can exploit this by tricking a user into opening a malicious file, allowing unauthorized memory access in the context of the current user.
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= 22.0.0.474CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Verify Corel Draw 2020 is installedOpen Windows Settings > Apps & Features or use Control Panel > Programs and Features to search for Corel Draw 2020 or CorelDRAW Graphics Suite 2020Affected if Corel Draw 2020 appears in the installed programs list
-
Check the installed version of Corel DrawRight-click on the Corel Draw application in the installed programs list and select 'Change/Properties' or look for version information; alternatively, right-click on CdrCore.dll in the Corel Draw program folder and select Properties > Details to view the file versionAffected if The version displayed is 22.0.0.474
-
Locate CdrCore.dll and verify its versionNavigate to the Corel Draw installation directory (typically C:\Program Files\Corel\CorelDRAW Graphics Suite 2020\ or similar), find CdrCore.dll, right-click and check Properties > Details for the file versionAffected if The CdrCore.dll file version shows 22.0.0.474
-
Confirm active use of CDR file parsingReview recent file open activity or check if the application is used to open CDR files from external or untrusted sourcesAffected if Users routinely open CDR files, particularly from untrusted sources, using the affected software version
A user is affected if Corel Draw 2020 version 22.0.0.474 is installed and the software is used to open CDR files, as the out-of-bounds read vulnerability in CdrCore.dll triggers when parsing specially crafted CDR files.
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 Corel Draw to the latest version that includes the security patch for this vulnerability. Until patched, avoid opening untrusted CDR files from unknown sources.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38107 — 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-2021-38107 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