CVE-2022-43615
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 · uneditedThis vulnerability allows remote attackers to disclose sensitive information on affected installations of Corel CorelDRAW Graphics Suite 23.5.0.506. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PDF files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-16370.
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 confidenceThis is an information disclosure vulnerability in CorelDRAW Graphics Suite's PDF parser. The vulnerability stems from insufficient validation of user-supplied data during PDF file parsing, allowing a read past the end of an allocated buffer. Exploitation requires user interaction (opening a malicious PDF file), and this flaw can be chained with other vulnerabilities to achieve arbitrary code execution.
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< 24.2.1CVSS 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.
-
Confirm CorelDRAW Graphics Suite is installedOpen Windows Settings > Apps > Installed apps, or check Add/Remove Programs, and look for CorelDRAW Graphics Suite in the list of installed software.Affected if CorelDRAW Graphics Suite appears in the installed programs list.
-
Identify the installed CorelDRAW version numberRight-click the CorelDRAW executable (usually located in C:\Program Files\Corel\CorelDRAW Graphics Suite XX\Programs\CorelDRAW.exe), select Properties, and view the Details tab for the Product Version. Alternatively, open CorelDRAW and go to Help > About CorelDRAW.Affected if A version number is displayed (for example, 24.0, 24.1, or any version shown).
-
Compare installed version against the vulnerable rangeCompare the identified version number to the vulnerable threshold. Versions prior to 24.2.1 are affected (for example, 24.0, 24.1.0, 23.5, etc.). Versions 24.2.1 and later are not vulnerable.Affected if The installed version is less than 24.2.1 (for example, 24.0.0.450, 23.5.0.301, etc.).
-
Verify the PDF parsing feature is accessibleConfirm that the PDF import or open functionality is available in the installed version. In CorelDRAW, attempt to import or open a PDF file via File > Open and verify PDF file type appears in the supported formats.Affected if The PDF file type is supported and can be opened in the installed version.
The environment is affected if CorelDRAW Graphics Suite is installed with a version lower than 24.2.1 and the PDF parsing feature can be used to open 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.
dbcve · scoped24.2.1
Users should avoid opening untrusted or unexpected PDF files from unverified sources. The vendor should patch the PDF parsing component to add proper bounds checking and validation of user-supplied data before reading operations.
CorelDRAW Graphics Suite 24.2.1 or later
- 1. Close any running instances of CorelDRAW Graphics Suite
- 2. Back up any important CorelDRAW files and preferences if desired
- 3. Navigate to the official Corel website or use the built-in update mechanism within CorelDRAW
- 4. Check for updates or navigate to the CorelDRAW Graphics Suite download page
- 5. Download and install CorelDRAW Graphics Suite version 24.2.1 or later
- 6. Restart your computer if prompted
- 7. Verify the installed version by opening CorelDRAW and checking About CorelDRAW in the Help menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43615 — 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-43615 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