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

Q: How do I fix CVE-2021-32614?

dmg2img: upgrade to newer than 20170502. Exact commands for each OS are on this page.

Q: Is CVE-2021-32614 being exploited?

CVE-2021-32614 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-32614 affect?

CVE-2021-32614 affects dmg2img. Severity is high (CVSS 7.1). 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 r

This month

HIGH 7.1UPGRADE

CVE-2021-32614 is a high-severity flaw (CVSS 7.1) affecting dmg2img. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-125
Published	2021-05-26
Last modified	2026-06-17

Publisher (CNA): Fedora Project · Vendor: dmg2img project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-05-26 22:15 UTCPublished CVE record published
2026-06-17 03:53 UTCUpdated Record last modified

dmg2img project dmg2img UPGRADE

Affected: <= 20170502

Fixed in: newer than 20170502

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dmg2img || rpm -q dmg2img || dmg2img --version

2. UPGRADE to newer than 20170502 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dmg2img

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dmg2img

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-32614?

dmg2img: upgrade to newer than 20170502. Exact commands for each OS are on this page.

Is CVE-2021-32614 being exploited?

CVE-2021-32614 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-32614 affect?

CVE-2021-32614 affects dmg2img. Severity is high (CVSS 7.1). 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 r

How urgent is CVE-2021-32614?

Priority 40/100. High severity

Related CVEs

CVE-2021-3548 HIGH 7.1 UPGRADE A flaw was found in dmg2img through 20170502

References

← Back to latest CVEs