{"id":"CVE-2021-32614","aliases":["DEBIAN-CVE-2021-32614","EUVD-2021-19452","GHSA-qw7r-wvwg-fj9h","UBUNTU-CVE-2021-32614"],"status":"published","title":"A flaw was found in dmg2img through 20170502. fill_mishblk() does not check the length of the...","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.","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00961,"percentile":0.62032,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-125"],"published":"2021-05-26T21:42:35Z","modified":"2026-10-23T18:03:37Z","affected":[{"source":"osv","ecosystem":"Debian:12","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7+git20201227.a3e4134-0.1","1.6.7-1"]},{"source":"osv","ecosystem":"Debian:13","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7+git20201227.a3e4134-0.1"]},{"source":"osv","ecosystem":"Debian:14","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7+git20201227.a3e4134-0.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.5-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.5-1.1","1.6.7-1","1.6.7-1build1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7-1build1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7-1build1","1.6.7-1build2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7-1build2","1.6.7-1build3","1.6.7-1build4"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7-1build4","1.6.7+git20201227.a3e4134-0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7+git20201227.a3e4134-0.1build1","1.6.7+git20201227.a3e4134-0.1build2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"dmg2img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7+git20201227.a3e4134-0.1","1.6.7+git20201227.a3e4134-0.1build1"]}],"products":[{"vendor":"dmg2img_project","product":"dmg2img"}],"references":[{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1959911","tags":["x_refsource_MISC","x_transferred","Issue Tracking","Third Party Advisory","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-32614"},{"url":"https://github.com/advisories/GHSA-qw7r-wvwg-fj9h"},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-32614","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-32614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-32614","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2021-32614","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.","status":"published","published":"2021-05-26T21:42:35Z","modified":"2024-08-03T23:25:30.625Z","cwes":["CWE-125"],"updated_at":"2026-11-02T14:33:07.014772Z"}],"euvd":[{"id":"EUVD-2021-19452","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.","status":"published","published":"2021-05-26T21:42:35Z","modified":"2024-08-03T23:25:30Z","updated_at":"2026-11-03T03:24:36.41075Z"}],"ghsa":[{"id":"GHSA-qw7r-wvwg-fj9h","title":"A flaw was found in dmg2img through 20170502. fill_mishblk() does not check the length of the...","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.","status":"published","published":"2022-05-24T19:03:33Z","modified":"2023-01-29T05:06:49Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:46:06.412268Z"}],"nvd":[{"id":"CVE-2021-32614","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.","status":"published","published":"2021-05-26T22:15:08.193Z","modified":"2026-06-17T03:53:16.51Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":5.8,"vector":"AV:N/AC:M/Au:N/C:P/I:N/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:06:53.987491Z"}],"osv":[{"id":"CVE-2021-32614","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.","status":"published","published":"2021-05-26T22:15:08.193Z","modified":"2026-03-14T10:58:28.577725Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:19.793849Z"},{"id":"DEBIAN-CVE-2021-32614","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.","status":"published","published":"2021-05-26T22:15:08.193Z","modified":"2026-10-23T18:03:37.631504793Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:35.233346Z"},{"id":"UBUNTU-CVE-2021-32614","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.","status":"published","published":"2021-05-26T22:15:00Z","modified":"2026-10-17T12:55:46.657634711Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:27.332852Z"}]}}