dbcve.org
CoreldrawApplication · Corel

CVE-2022-43618

HIGH · 7.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 24.2.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
This vulnerability allows remote attackers to execute arbitrary code 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 PCX files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16377.

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 confidence

Buffer overflow vulnerability in CorelDRAW Graphics Suite's PCX file parser. The lack of proper validation of user-supplied data during PCX file parsing allows writing past the end of an allocated buffer, enabling arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Corel when available; avoid opening untrusted PCX files from unknown or untrusted sources.

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
CoreldrawApplication
Affected:< 24.2.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CorelDRAW Graphics Suite installation
    Open CorelDRAW and go to Help > About CorelDRAW, or check Programs and Features in Control Panel for the installed version
    Affected if The displayed version is lower than 24.2.1 or not shown as version 24.2.1 or higher
  2. Confirm PCX file support is present
    CorelDRAW typically includes PCX import capability by default. To verify, attempt to open a PCX file or check File > Open with .pcx extension visible in the filter list
    Affected if PCX file format is available in the open dialog filters (indicates the vulnerable parser component is present)
  3. Compare installed version against affected range
    Note the exact version number from step 1 and compare: any version below 24.2.1 (such as 24.x.x versions before 24.2.1, or any 23.x, 22.x, older versions) falls within the affected range
    Affected if The installed version is any release prior to 24.2.1

You are affected if CorelDRAW Graphics Suite is installed with any version lower than 24.2.1 and the PCX file import feature is present in your installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 24.2.1 or later
Fixed in 24.2.1
Interim mitigation

Apply vendor patches from Corel when available; avoid opening untrusted PCX files from unknown or untrusted sources.

Recommended fix High confidence

CorelDRAW Graphics Suite 24.2.1

  1. Open CorelDRAW Graphics Suite and navigate to Help > About CorelDRAW to confirm the current installed version
  2. If the version is below 24.2.1, download CorelDRAW Graphics Suite version 24.2.1 or later from the official Corel website (www.corel.com)
  3. Close all CorelDRAW applications before running the installer
  4. Run the downloaded installer with administrator privileges and follow the on-screen prompts to complete the upgrade
  5. After installation, verify the new version by checking Help > About CorelDRAW to confirm version 24.2.1 or higher is installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coreldraw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43618 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43618 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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