Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| — | dmg2img | dmg2img through 20170502 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | dmg2img | No fix yet | — |
| Debian 13 | dmg2img | No fix yet | — |
| Debian 12 | dmg2img | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | dmg2img | No fix yet | — |
| Ubuntu 26.04 LTS | dmg2img | No fix yet | — |
| Ubuntu 25.10 | dmg2img | No fix yet | — |
| Ubuntu 24.04 LTS | dmg2img | No fix yet | — |
| Ubuntu 22.04 LTS | dmg2img | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | dmg2img | No fix yet | — |
| Ubuntu 18.04 LTS | dmg2img | No fix yet | — |
| Ubuntu 16.04 LTS | dmg2img | No fix yet | — |