CVE-2022-43612
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 JP2 images. 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-16355.
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 confidenceCorelDRAW Graphics Suite 23.5.0.506 contains an out-of-bounds read vulnerability when parsing JP2 (JPEG 2000) image files. The application fails to properly validate user-supplied data during JP2 parsing, allowing an attacker to read past the end of an allocated memory buffer. Successful exploitation requires user interaction (opening a malicious file or visiting a malicious page), and this vulnerability can be chained with other flaws 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 installationCheck for CorelDRAW installation by looking in standard locations: C:\Program Files\Corel\ or C:\Program Files (x86)\Corel\, or query the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Corel or HKEY_CURRENT_USER\SOFTWARE\CorelAffected if CorelDRAW Graphics Suite is not found on the system, then the CVE does not apply
-
Identify installed versionLocate the main CorelDRAW executable (typically coreldrw.exe or similar) in the installation folder, right-click and select Properties, or use command: dir /s "C:\Program Files\Corel\*coreldrw.exe" to find the path, then check the version tab in PropertiesAffected if The installed version number is lower than 24.2.1 (for example, 23.5.0.506 or any version < 24.2.1)
-
Verify JP2 file handling capabilityCheck if the CorelDRAW installation includes JP2 (JPEG 2000) image format support by looking for related filters in the installation directory (often in a Filters or Plugins subfolder), or attempt to open a .jp2 file in CorelDRAW to confirm parsing capability is presentAffected if JP2 parsing functionality is present and the version is < 24.2.1, then the vulnerability is exploitable
-
Check file association exposureExamine whether .jp2 file extensions are associated with CorelDRAW by right-clicking any .jp2 file in Windows Explorer, selecting Properties, and viewing the 'Opens with' section, or by checking HKEY_CLASSES_ROOT\.jp2 in the Windows RegistryAffected if CorelDRAW is set as the default handler for .jp2 files and the version is vulnerable, increasing the likelihood of accidental exploitation
The environment is affected if CorelDRAW Graphics Suite version 24.2.1 or higher is NOT installed AND the JP2 file parsing feature is present and accessible on the system.
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
Avoid opening untrusted JP2 files or downloading from untrusted sources until Corel releases an official patch. Restrict usage of CorelDRAW to trusted files and consider deploying additional endpoint protection to detect malicious file parsing attempts.
CorelDRAW Graphics Suite 24.2.1 or later
- Backup all existing CorelDRAW projects and settings before upgrading
- Navigate to the official Corel website (www.corel.com) and download CorelDRAW Graphics Suite version 24.2.1 or later
- Uninstall the current vulnerable version of CorelDRAW Graphics Suite
- Install the downloaded version 24.2.1 or later
- Verify the installation was successful and confirm the version number in the application's About section
- Avoid opening untrusted JP2 image files from unknown sources as a secondary precaution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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 $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43612 — 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-43612 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