Debian Package Tracker
Register | Log in
Subscribe

libimager-perl

Perl extension for generating 24-bit images

Choose email to subscribe with

general
  • source: libimager-perl (main)
  • version: 1.033+dfsg-1
  • maintainer: Debian Perl Group (archive) (DMD) (LowNMU)
  • uploaders: Damyan Ivanov [DMD] – gregor herrmann [DMD] – Dominic Hargreaves [DMD]
  • arch: any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 1.012+dfsg-1
  • oldstable: 1.019+dfsg-1
  • stable: 1.027+dfsg-1
  • testing: 1.033+dfsg-1
  • unstable: 1.033+dfsg-1
versioned links
  • 1.012+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.019+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.027+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.033+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libimager-perl
action needed
5 security issues in bullseye high

There are 5 open security issues in bullseye.

3 important issues:
  • CVE-2026-13705: Imager versions before 1.032 for Perl have a heap out-of-bounds read in the bundled Imager::File::SGI reader via a 16-bit RLE literal run in read_rgb_16_rle. read_rgb_16_rle guards each literal run with if (count > data_left), but count is a pixel count while every 16-bit sample consumes two bytes. The copy loop reads inp[0] * 256 + inp[1] and advances two bytes per pixel, so a run with data_left / 2 < count <= data_left passes the guard yet consumes 2 * count bytes and reads past the end of the buffer. The 8-bit path is unaffected because there one pixel is one byte. Reading a crafted SGI image through Imager->read triggers the over-read before the parser rejects the malformed image, which can crash the process.
  • CVE-2026-13708: Imager::File::JPEG versions before 1.003 for Perl leak heap memory when reading a JPEG with repeated APP13 markers in i_readjpeg_wiol. i_readjpeg_wiol walks the marker list libjpeg returns and, for each APP13 marker, allocates a new buffer with *iptc_itext = mymalloc(...) and overwrites the previous pointer without freeing it. Only the final payload is later turned into a Perl scalar and freed, so a JPEG with N such markers leaks the first N-1 payloads on every read. In a long-lived process, such as an upload or thumbnailing service, repeated reads accumulate these leaks and exhaust available memory, a denial of service. The same handler ships bundled in the Imager distribution, where versions before 1.032 are affected and the fix ships in 1.032.
  • CVE-2026-14454: Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed. Imager mishandled large EXIF IFD entry count values, treating them as negative numbers. This could lead to an attempt to allocate a block nearly the size of the address space, which fails and kills the process. An attacker could craft an image with EXIF data that terminates a worker process.
2 issues postponed or untriaged:
  • CVE-2026-8669: (needs triaging) Imager versions through 1.030 for Perl allow a heap out of bounds (OOB) write on crafted multi-frame GIF files. Imager::File::GIF's i_readgif_multi_low allocates a single per-row buffer GifRow sized for the GIF's global screen width 'SWidth' and reuses it across every image in the file. The page-match branch validates Image.Width + Image.Left > SWidth before each DGifGetLine write, but the parallel skip-image branch at imgif.c:790-805 calls DGifGetLine(GifFile, GifRow, Width) with no such check.
  • CVE-2024-53901: (postponed; to be fixed through a stable update) The Imager package before 1.025 for Perl has a heap-based buffer overflow leading to denial of service, or possibly unspecified other impact, when the trim() method is called on a crafted input image.
Created: 2026-07-06 Last update: 2026-07-15 08:30
5 security issues in bookworm high

There are 5 open security issues in bookworm.

3 important issues:
  • CVE-2026-13705: Imager versions before 1.032 for Perl have a heap out-of-bounds read in the bundled Imager::File::SGI reader via a 16-bit RLE literal run in read_rgb_16_rle. read_rgb_16_rle guards each literal run with if (count > data_left), but count is a pixel count while every 16-bit sample consumes two bytes. The copy loop reads inp[0] * 256 + inp[1] and advances two bytes per pixel, so a run with data_left / 2 < count <= data_left passes the guard yet consumes 2 * count bytes and reads past the end of the buffer. The 8-bit path is unaffected because there one pixel is one byte. Reading a crafted SGI image through Imager->read triggers the over-read before the parser rejects the malformed image, which can crash the process.
  • CVE-2026-13708: Imager::File::JPEG versions before 1.003 for Perl leak heap memory when reading a JPEG with repeated APP13 markers in i_readjpeg_wiol. i_readjpeg_wiol walks the marker list libjpeg returns and, for each APP13 marker, allocates a new buffer with *iptc_itext = mymalloc(...) and overwrites the previous pointer without freeing it. Only the final payload is later turned into a Perl scalar and freed, so a JPEG with N such markers leaks the first N-1 payloads on every read. In a long-lived process, such as an upload or thumbnailing service, repeated reads accumulate these leaks and exhaust available memory, a denial of service. The same handler ships bundled in the Imager distribution, where versions before 1.032 are affected and the fix ships in 1.032.
  • CVE-2026-14454: Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed. Imager mishandled large EXIF IFD entry count values, treating them as negative numbers. This could lead to an attempt to allocate a block nearly the size of the address space, which fails and kills the process. An attacker could craft an image with EXIF data that terminates a worker process.
2 issues left for the package maintainer to handle:
  • CVE-2026-8669: (needs triaging) Imager versions through 1.030 for Perl allow a heap out of bounds (OOB) write on crafted multi-frame GIF files. Imager::File::GIF's i_readgif_multi_low allocates a single per-row buffer GifRow sized for the GIF's global screen width 'SWidth' and reuses it across every image in the file. The page-match branch validates Image.Width + Image.Left > SWidth before each DGifGetLine write, but the parallel skip-image branch at imgif.c:790-805 calls DGifGetLine(GifFile, GifRow, Width) with no such check.
  • CVE-2024-53901: (needs triaging) The Imager package before 1.025 for Perl has a heap-based buffer overflow leading to denial of service, or possibly unspecified other impact, when the trim() method is called on a crafted input image.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-11-24 Last update: 2026-07-15 08:30
4 low-priority security issues in trixie low

There are 4 open security issues in trixie.

4 issues left for the package maintainer to handle:
  • CVE-2026-8669: (needs triaging) Imager versions through 1.030 for Perl allow a heap out of bounds (OOB) write on crafted multi-frame GIF files. Imager::File::GIF's i_readgif_multi_low allocates a single per-row buffer GifRow sized for the GIF's global screen width 'SWidth' and reuses it across every image in the file. The page-match branch validates Image.Width + Image.Left > SWidth before each DGifGetLine write, but the parallel skip-image branch at imgif.c:790-805 calls DGifGetLine(GifFile, GifRow, Width) with no such check.
  • CVE-2026-13705: (needs triaging) Imager versions before 1.032 for Perl have a heap out-of-bounds read in the bundled Imager::File::SGI reader via a 16-bit RLE literal run in read_rgb_16_rle. read_rgb_16_rle guards each literal run with if (count > data_left), but count is a pixel count while every 16-bit sample consumes two bytes. The copy loop reads inp[0] * 256 + inp[1] and advances two bytes per pixel, so a run with data_left / 2 < count <= data_left passes the guard yet consumes 2 * count bytes and reads past the end of the buffer. The 8-bit path is unaffected because there one pixel is one byte. Reading a crafted SGI image through Imager->read triggers the over-read before the parser rejects the malformed image, which can crash the process.
  • CVE-2026-13708: (needs triaging) Imager::File::JPEG versions before 1.003 for Perl leak heap memory when reading a JPEG with repeated APP13 markers in i_readjpeg_wiol. i_readjpeg_wiol walks the marker list libjpeg returns and, for each APP13 marker, allocates a new buffer with *iptc_itext = mymalloc(...) and overwrites the previous pointer without freeing it. Only the final payload is later turned into a Perl scalar and freed, so a JPEG with N such markers leaks the first N-1 payloads on every read. In a long-lived process, such as an upload or thumbnailing service, repeated reads accumulate these leaks and exhaust available memory, a denial of service. The same handler ships bundled in the Imager distribution, where versions before 1.032 are affected and the fix ships in 1.032.
  • CVE-2026-14454: (needs triaging) Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed. Imager mishandled large EXIF IFD entry count values, treating them as negative numbers. This could lead to an attempt to allocate a block nearly the size of the address space, which fails and kills the process. An attacker could craft an image with EXIF data that terminates a worker process.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-05-15 Last update: 2026-07-15 08:30
testing migrations
  • This package will soon be part of the perl-5.42 transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
news
[rss feed]
  • [2026-07-15] libimager-perl 1.033+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-07-12] Accepted libimager-perl 1.033+dfsg-1 (source) into unstable (gregor herrmann)
  • [2026-07-09] libimager-perl 1.032+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-07-06] Accepted libimager-perl 1.032+dfsg-1 (source) into unstable (gregor herrmann)
  • [2026-05-25] libimager-perl 1.031+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-05-15] Accepted libimager-perl 1.031+dfsg-1 (source) into unstable (Samuel Young) (signed by: gregor herrmann)
  • [2026-04-18] libimager-perl 1.030+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-04-15] Accepted libimager-perl 1.030+dfsg-1 (source) into unstable (Samuel Young) (signed by: gregor herrmann)
  • [2025-10-13] libimager-perl 1.029+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-10] Accepted libimager-perl 1.029+dfsg-1 (source) into unstable (gregor herrmann)
  • [2025-10-09] libimager-perl 1.028+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-06] Accepted libimager-perl 1.028+dfsg-1 (source) into unstable (gregor herrmann)
  • [2025-03-19] libimager-perl 1.027+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-03-16] Accepted libimager-perl 1.027+dfsg-1 (source) into unstable (gregor herrmann)
  • [2024-11-25] libimager-perl 1.025+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-11-23] Accepted libimager-perl 1.025+dfsg-1 (source) into unstable (gregor herrmann)
  • [2024-09-17] libimager-perl 1.024+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2024-09-15] Accepted libimager-perl 1.024+dfsg-2 (source) into unstable (gregor herrmann)
  • [2024-05-03] libimager-perl 1.024+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-04-13] Accepted libimager-perl 1.024+dfsg-1 (source) into unstable (gregor herrmann)
  • [2024-01-23] libimager-perl 1.023+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-01-20] Accepted libimager-perl 1.023+dfsg-1 (source) into unstable (gregor herrmann)
  • [2023-12-05] libimager-perl 1.022+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2023-12-03] Accepted libimager-perl 1.022+dfsg-1 (source) into unstable (gregor herrmann)
  • [2023-11-20] libimager-perl 1.020+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2023-11-17] Accepted libimager-perl 1.020+dfsg-1 (source) into unstable (gregor herrmann)
  • [2023-07-21] libimager-perl 1.019+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2023-07-17] Accepted libimager-perl 1.019+dfsg-2 (source) into unstable (gregor herrmann)
  • [2022-07-13] libimager-perl 1.019+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-09] Accepted libimager-perl 1.019+dfsg-1 (source) into unstable (gregor herrmann)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1.031+dfsg-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing