https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-25T13:44:42.384480+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2021-04866 bdu:2021-04866 2026-10-25T13:44:42.387996+00:00 bdu:2021-04866 https://cve.radiocsirt.org/vuln/euvd-2026-27989 EUVD-2026-27989 2026-10-25T13:44:42.388026+00:00 EUVD-2026-27989 https://cve.radiocsirt.org/vuln/fkie_cve-2021-32614 fkie_cve-2021-32614 2026-10-25T13:44:42.388040+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-qw7r-wvwg-fj9h GHSA-qw7r-wvwg-fj9h 2026-10-25T13:44:42.388069+00:00

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.

 https://cve.radiocsirt.org/vuln/gsd-2021-32614 gsd-2021-32614 2026-10-25T13:44:42.388086+00:00 gsd-2021-32614 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-32614 UBUNTU-CVE-2021-32614 2026-10-25T13:44:42.388097+00:00

Affected: Ubuntu:16.04:LTS: dmg2img, Ubuntu:18.04:LTS: dmg2img, Ubuntu:20.04:LTS: dmg2img, Ubuntu:22.04:LTS: dmg2img, Ubuntu:24.04:LTS: dmg2img, Ubuntu:25.10: dmg2img, Ubuntu:26.10: dmg2img, Ubuntu:26.04:LTS: dmg2img

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.