# CVE-2022-48622: Memory corruption in n/a

> Heap memory corruption in GdkPixbuf's ANI decoder allows attackers to execute code or cause denial of service via crafted files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jan 2024
- **Updated:** 26 Aug 2024
- **Also known as:** ALPINE-CVE-2022-48622, ALSA-2024:3341, ALSA-2024:3834, AZL-34069, AZL-34726, BELL-CVE-2022-48622, CLSA-2025-1758824659, DEBIAN-CVE-2022-48622, GHSA-2pj9-xmx5-6fv3, MGASA-2024-0182, OESA-2024-2039, OESA-2024-2040, OESA-2024-2143, OESA-2024-2144, OESA-2024-2145, RHSA-2024:3341, RHSA-2024:3834, RLSA-2024:3341, RLSA-2024:3834, SUSE-SU-2024:1699-1, SUSE-SU-2024:1842-1, SUSE-SU-2024:2076-1, SUSE-SU-2024:2077-1, SUSE-SU-2024:2077-2, SUSE-SU-2025:20217-1, UBUNTU-CVE-2022-48622, USN-6806-1, openSUSE-SU-2024:13967-1

## What is CVE-2022-48622?

CVE-2022-48622 is a high-severity memory corruption vulnerability in n/a, published on 26 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In GNOME GdkPixbuf (aka gdk-pixbuf) through 2.42.10, the ANI (Windows animated cursor) decoder encounters heap memory corruption (in ani_load_chunk in io-ani.c) when parsing chunks in a crafted .ani file. A crafted file could allow an attacker to overwrite heap metadata, leading to a denial of service or code execution attack. This occurs in gdk_pixbuf_set_option() in gdk-pixbuf.c.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-48622?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gdk-pixbuf2` | AlmaLinux:8 | All versions | 2.36.12-6.el8_10 |
| `gdk-pixbuf2-devel` | AlmaLinux:8 | All versions | 2.36.12-6.el8_10 |
| `gdk-pixbuf2-modules` | AlmaLinux:8 | All versions | 2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib` | AlmaLinux:8 | All versions | 2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib-devel` | AlmaLinux:8 | All versions | 2.36.12-6.el8_10 |
| `gdk-pixbuf2` | AlmaLinux:9 | All versions | 2.42.6-4.el9_4 |
| `gdk-pixbuf2-devel` | AlmaLinux:9 | All versions | 2.42.6-4.el9_4 |
| `gdk-pixbuf2-modules` | AlmaLinux:9 | All versions | 2.42.6-4.el9_4 |
| `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-modules` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2-xlib-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.36.12-6.el8_10 |
| `gdk-pixbuf2` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-modules` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-modules-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2-tests-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.42.6-4.el9_4 |
| `gdk-pixbuf2` | Rocky Linux:8 | All versions | 0:2.36.12-6.el8_10 |

Products: Gnome Gdkpixbuf.

## How do I fix CVE-2022-48622?

Upgrade to a fixed version.

## Is CVE-2022-48622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48622 exists.

## Other vulnerabilities in n/a

- [CVE-2005-2975](https://insights.sbomify.com/CVE-2005-2975/): Denial of service in n/a (high 7.8)
- [CVE-2005-2976](https://insights.sbomify.com/CVE-2005-2976/): Integer overflow in n/a (high 7.5)
- [CVE-2005-3186](https://insights.sbomify.com/CVE-2005-3186/): Integer overflow in n/a (high 7.5)
- [CVE-2004-0782](https://insights.sbomify.com/CVE-2004-0782/): Integer overflow in n/a (high 7.5)
- [CVE-2004-0783](https://insights.sbomify.com/CVE-2004-0783/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48622 and fix it if it is affected.

What it is: CVE-2022-48622 is a high-severity memory corruption vulnerability in n/a, published on 26 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48622 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48622/ (Markdown: https://insights.sbomify.com/CVE-2022-48622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48622
- OSV: https://osv.dev/vulnerability/CVE-2022-48622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48622/
Summaries are generated and may contain mistakes; the official description above is the record.