CVE-2023-3745: Imagemagick: heap-buffer-overflow in pushcharpixel() in quantum-private.h
A heap-based buffer overflow issue was found in ImageMagick's PushCharPixel() function in quantum-private.h. This issue may allow a local attacker to trick the user into opening a specially crafted file, triggering an out-of-bounds read error and allowing an application to crash, resulting in a denial of service.
Security readout for executives and security teams
Plain-English summary
CVE-2023-3745 is an ImageMagick flaw that can crash an application when a user opens a specially crafted image file. The cited impact is denial of service, not data theft or code execution. Business urgency is moderate for systems processing untrusted images, especially user-upload workflows.
Executive priority
Treat as a moderate availability risk. Prioritize internet-facing or customer-facing image-processing services first. This is not currently evidenced as actively exploited in the provided sources, but a crafted file could disrupt affected workflows.
Technical view
ImageMagick has a heap-based buffer overflow/out-of-bounds read in PushCharPixel() in quantum-private.h. CVSS 3.1 is 5.5, local attack vector, low complexity, no privileges, user interaction required, high availability impact. Red Hat lists ImageMagick packages for RHEL 6 and 7 in the provided affected data.
Likely exposure
Exposure is most likely where ImageMagick handles files from users, partners, email, web uploads, or automated media pipelines. The attacker must get a crafted file opened or processed. Systems not processing untrusted image files have lower practical exposure.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The described scenario requires user interaction or application processing of a crafted file. Public references include upstream ImageMagick commits and an issue, but no source here proves active exploitation.
Researcher notes
The record names PushCharPixel() in quantum-private.h and CWE-125, while describing heap-based buffer overflow and out-of-bounds read leading to crash. Provided affected Red Hat entries lack explicit fixed versions. Use vendor advisories and referenced upstream commits to map exact package exposure.
Mitigation direction
Check Red Hat and ImageMagick guidance for fixed package or release information.
Prioritize systems that process untrusted image uploads or attachments.
Restrict ImageMagick processing of untrusted files where business workflows allow.
Run image conversion services with least privilege and isolation.
Retire or tightly control unsupported RHEL 6 systems if present.
Validation and detection
Inventory ImageMagick installations, especially on RHEL 6 and RHEL 7.
Identify applications that automatically process externally supplied images.
Compare installed packages against vendor advisory status and fixed upstream commits.
Review crash reports for ImageMagick-related processing failures.
Confirm compensating controls around upload validation and sandboxing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.