CVE-2025-7345: Gdk‑pixbuf: heap‑buffer‑overflow in gdk‑pixbuf
A flaw exists in gdk‑pixbuf within the gdkpixbufjpegimageloadincrement function (io-jpeg.c) and in glib’s gbase64encodestep (glib/gbase64.c). When processing maliciously crafted JPEG images, a heap buffer overflow can occur during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially causing application crashes or arbitrary code execution.
Other sources
Heap‑buffer‑overflow vulnerability in the JPEG and Base64 decoding paths of gdk‑pixbuf. The flaw occurs in gdkpixbufjpegimageloadincrement() (io‑jpeg.c:1193:26) when a specially crafted JPEG triggers a flow that leads to gbase64encodestep() in glib (gbase64.c:141:16), reading beyond heap buffer bounds. Exploitation requires no authentication and could lead to application crash or arbitrary code execution via crafted images.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-7345?
CVE-2025-7345 has been classified as a high severity vulnerability due to the potential for a heap buffer overflow.
How do I fix CVE-2025-7345?
To fix CVE-2025-7345, update gdk-pixbuf and glib to the latest versions that contain patches addressing this vulnerability.
What are the potential impacts of CVE-2025-7345?
The potential impacts of CVE-2025-7345 include application crashes and possible remote code execution if exploited.
Which software is affected by CVE-2025-7345?
CVE-2025-7345 affects GNOME's gdk-pixbuf and glib libraries.
How can I mitigate the risk associated with CVE-2025-7345?
Mitigation of CVE-2025-7345 involves applying security patches and ensuring that JPEG processing in applications is handled securely.