CVE-2022-43611
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 BMP 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-16351.
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 confidenceAn out-of-bounds read vulnerability in CorelDRAW Graphics Suite 23.5.0.506's BMP image parser allows remote attackers to disclose sensitive information by parsing malicious BMP files without proper validation of user-supplied data. While user interaction is required (opening a malicious file), this can be chained with other vulnerabilities for 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 examining the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM\SOFTWARE\Corel, or look for CorelDRAW executables in Program Files directoriesAffected if CorelDRAW Graphics Suite is installed on the system
-
Identify installed CorelDRAW versionLocate the CorelDRAW executable (typically in Program Files\Corel\CorelDRAW Graphics Suite X) and check its properties for the version, or query the Windows Registry for the DisplayVersion value under the CorelDRAW uninstall keyAffected if The installed version is lower than 24.2.1 (e.g., 23.5.0.506 or earlier)
-
Verify BMP file handling capabilityConfirm the CorelDRAW installation includes BMP import functionality by checking if BMP file type is associated with the software or by inspecting installed import filtersAffected if BMP file import/export capabilities are present in the installation
-
Check for recent file opening activityReview application logs, Windows Event Viewer for Application logs, or recently opened files in CorelDRAW to identify any recent BMP file processingAffected if Users have opened untrusted BMP files in CorelDRAW
A system is affected if CorelDRAW Graphics Suite version 24.2.1 or earlier is installed and users can open BMP files with the software.
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
Deploy the vendor patch from Corel when available. Until then, enforce user awareness to avoid opening untrusted BMP files and consider application whitelisting to restrict execution of untrusted graphics utilities.
CorelDRAW Graphics Suite 24.2.1 or later
- Verify your current CorelDRAW version by opening the application and navigating to Help > About CorelDRAW
- Close any running instances of CorelDRAW
- Download CorelDRAW Graphics Suite version 24.2.1 or later from the official Corel website (https://www.coreldraw.com)
- Run the installer and follow the on-screen prompts to complete the upgrade
- After installation, verify the new version by checking Help > About CorelDRAW to confirm version 24.2.1 or higher is installed
- Exercise caution when opening BMP files from untrusted sources, even after patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43611 — 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-43611 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