GIMP ICO File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of…
GIMP FLI File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing…
GIMP XWD File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of…
A flaw was found in the file-psd plugin in GIMP. When processing a specially crafted PSD image file, the plugin does not properly validate the channel-count parameter. This incorrect validation leads to improper memory bounds checking, resulting in both a heap out-of-bounds read and a stack out-of-bounds access. This issue can result in an application crash…
A flaw was found in the file-ico plugin in GIMP. When processing a specially crafted ICO image file, the plugin does not properly validate the used_clrs (palette count) parameter. This incorrect validation leads to improper memory bounds checking, resulting in a heap out-of-bounds read. This issue can result in an application crash, leading to a denial of s…
A flaw was found in the file-pvr plugin in GIMP. When processing a specially crafted PVR image file, the VQ (compressed) decoder does not properly perform memory bounds checking. This missing validation results in a heap out-of-bounds read. This issue can result in an application crash, leading to a denial of service or a limited information disclosure of h…
A flaw was found in the file-iff (IFF/ILBM) plugin in GIMP. When processing a specially crafted IFF/ILBM image file, the plugin does not properly validate the HAM row size and improperly handles cases where the number of color planes (nPlanes) is zero. This causes a row size mismatch that bypasses memory bounds checking, resulting in heap out-of-bounds read…
A flaw was found in GIMP's PSP file format parser. A double-free condition occurs in the read_layer_block() function when processing a specially crafted PSP file. This could allow an attacker to cause memory corruption, potentially leading to denial of service or arbitrary code execution.
A flaw was found in GIMP. This issue is a heap buffer over-read in GIMP PCX file loader due to an off-by-one error. A remote attacker could exploit this by convincing a user to open a specially crafted PCX image. Successful exploitation could lead to out-of-bounds memory disclosure and a possible application crash, resulting in a Denial of Service (DoS).
A flaw was found in the Seattle FilmWorks plugin in GIMP. When processing a specially crafted SFW image file, the plugin allocates a Variable-Length Array (VLA) on the stack without integer overflow checks, causing an unbounded stack allocation. This issue leads to an application crash, resulting in a denial of service.
A flaw was found in the file-xwd plugin in GIMP. When processing a specially crafted XWD image file, the plugin validates the image width and bytes-per-line parameters independently rather than ensuring their combined values are consistent with the allocated buffer size. This incorrect validation leads to improper bounds checking, causing a heap out-of-boun…
VuXML only (0) · listed, port not fixed yet
None. pkg audit reports nothing for this version.
Fixed (1)
VuXML entries whose affected range this version has left.
graphics/gimp-app: fpsetmask() -> fedisableexcept()
Replace the use of the older fpsetmask() call with fedisableexcept().
The build previously only succeeded on armv7 due to ANSI C semantics
in which it is permitted to call an undlecared function.
Approved by: portmgr (build fix blanket)
MFH: 2025Q4
graphics/gimp3-app: add GIMP 3 to the ports tree (+)
Add GIMP 3.0.2 as separate port until plugins (including GutenPring) will not be ported to new API
Ancient MNG support is disabled and marked as BROKEN, our graphics/libmng port is borked by design
Release notes: https://www.gimp.org/news/2025/03/16/gimp-3-0-released/ \
https://www.gimp.org/news/2025/03/23/gimp-3-0-2-released/
graphics/gimp-app: patch configure.ac instead of configure
This makes importing upstream commits or merge requests easier in
addition to keeping track of our changes. Pre-generated configure
scripts are only present in release tarballs, but all modifications
after/separate from the fact only happen in configure.ac, so generate
the configure script every time.
graphics/gimp-app: fix build with libheif-1.18.1
libheif codecs can be dynamically loaded and it is not possible anymore
to determine available codecs at compile time. Assume the required codecs
are always available.
graphics/gimp{,-app}: sort out Makefile and pet portclippy
Changes:
- converted to DISTVERSION;
- pet protclippy;
- alphabetical sort options;
- removed SLAVE code - the port has had no slaves for several years;
- other minor changes.
PR: 279306
Approved by: fluffy (gnome, maintainer)
graphics/libjxl: force rebuild consumers after 4c1f4b3f46bc
$ ffmpeg
ld-elf.so.1: Shared object "libjxl.so.0.9" not found, required by "libavcodec.so.60"
Reported by: vvd
graphics/gimp-app: update to 2.10.36 release (+)
New features and improvements:
* ASE and ACB palettes support
* New Gradient: FG to Transparent (Hardedge)
* GIF: non-square ratio support
* More enhancements
Security and bug fixes:
* Fixed Vulnerabilities
* Broken Graphics Tablets with recent linuxwacom driver
Read more: https://www.gimp.org/news/2023/11/07/gimp-2-10-36-released/
accessibility/at-spi2-core: update to 2.46.0
What's new in at-spi2-core 2.46.0:
* Fix GetInterfaces documentation on org.a11y.atspi.Accessible
interface.
What's new in at-spi2-core 2.45.91:
* Send device event controller events using the same signature as other
events.
* Document the Accessible, Action, and Cache dbus interfaces.
* Fix license of atspi-gmain.c (#87).
What's new in at-spi2-core 2.45.90:
* xml: Add some documentation.
* xml: Fix event arguments.
* xml: Add some missing DeviceEventController methods.
* Bind the AT-SPI bus to the graphical session.
* Mark bus service as belonging to the session slice.
* Add ATSPI_ROLE_PUSH_BUTTON_MENU.
* Add an "announcement" event/signal to allow objects to send
notifications (!63).
* Various code clean-ups and test improvements.
What's new in at-spi2-core 2.45.1:
* Atk and at-spi2-atk are now merged into this project.
* Now requires meson 0.56.2 and glib 2.67.4.
* at-spi2-atk: Expose the accessible hierarchy via dbus introspection.
* Properly escape the AT-SPI bus address; fixes warnings about the address
not containing a colon (!55).
* Add a text value to AtspiValue, so that a value can expose a textual
description, as in the new Atk value API.
* Add atspi_event_listener_register_with_app, to allow an event listener
to be registered only for a given application (!52).
- accessibility/atk and accessibility/at-spi2-atk have been merged into
accessibility/at-spi2-core
- accessibility/at-spi2-core: bump consumers of removed ports atk and at-spi2-atk
PR: 269704
Exp-run by: antoine
---
graphics/gimp-app: fix build with clang 15
During an exp-run for llvm 15 (see bug 265425), it turned out that
graphics/gimp-app failed to build with clang 15:
file-dicom.c:605:26: error: incompatible pointer to integer conversion returning 'void *' from a function with result type 'gint32' (aka 'int') [-Wint-conversion]
return NULL;
^~~~
This is because the return statement is a function that should return an
integer, not a pointer. Replace it with the error value -1, as used
elsewhere in the function.
PR: 268790
Approved by: fluffy (maintainer)
MFH: 2023Q1
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)