LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32614: A flaw was found in dmg2img through 20170502.

A flaw was found in dmg2img through 20170502. fill_mishblk() does not check the length of the read buffer, and copy 0xCC bytes from it. The length of the buffer is controlled by an attacker. By providing a length smaller than 0xCC, memcpy reaches out of the malloc'ed bound. This possibly leads to memory layout information leaking in the data. This might be used in a chain of vulnerability in order to reach code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

dmg2img through 20170502 can read past the end of an attacker-controlled buffer while handling input. The public record says this may leak memory layout information and could help a larger exploit chain. No CVSS score, confirmed patch, or active exploitation evidence is provided in the supplied sources.

Executive priority

Treat this as a targeted hygiene issue, not an emergency, unless dmg2img handles untrusted files in production or security-sensitive workflows. Prioritize inventory and containment first because public fix details are incomplete.

Technical view

The flaw is in fill_mishblk(), which copies 0xCC bytes without verifying the read buffer length. If attacker-controlled length is smaller than 0xCC, memcpy reads beyond the malloc allocation. The CVE maps this to CWE-125 out-of-bounds read, with possible memory information disclosure.

Likely exposure

Exposure is limited to environments using dmg2img through 20170502, especially where the tool processes files supplied by untrusted users, customers, partners, or automated intake pipelines.

Exploitation context

The supplied sources do not show active exploitation or CISA KEV listing. The described impact is information disclosure that might support a broader vulnerability chain, not standalone confirmed code execution.

Researcher notes

The core condition is a length mismatch before a fixed-size memcpy in fill_mishblk(). Evidence supports out-of-bounds read and possible memory layout disclosure. The supplied record does not provide PoC details, exploit maturity, affected platforms, or remediation commits.

Mitigation direction

  • Inventory dmg2img installations and identify versions through 20170502.
  • Check vendor, distribution, or package maintainer guidance for fixed builds or backports.
  • Avoid processing untrusted dmg2img inputs until remediation guidance is confirmed.
  • Run required conversions in isolated, least-privileged processing environments.

Validation and detection

  • Confirm whether dmg2img is installed on servers, workstations, containers, or build images.
  • Review workflows for automated processing of untrusted disk image inputs.
  • Check package manager metadata for dmg2img version and distribution backport notes.
  • Monitor vendor advisories for a named fix or mitigation.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32614 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/admg2imgdmg2img through 20170502Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.