# CVE-2021-46822: Memory corruption in n/a > Heap-based buffer overflow in libjpeg-turbo PPM reader allows attackers to execute arbitrary code or cause denial of service via crafted images. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 18 Jun 2022 - **Updated:** 4 Aug 2024 - **Also known as:** ALSA-2023:1068, DEBIAN-CVE-2021-46822, GHSA-p468-hq86-gghc, JLSEC-2025-180, MGASA-2022-0353, OESA-2022-1745, RHSA-2023:1068, RLSA-2023:1068, ROOT-OS-DEBIAN-11-CVE-2021-46822, UBUNTU-CVE-2021-46822 ## What is CVE-2021-46822? CVE-2021-46822 is a medium-severity memory corruption vulnerability in n/a, published on 18 Jun 2022. 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 The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2021-46822? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libjpeg-turbo` | AlmaLinux:9 | All versions | 2.0.90-6.el9_1 | | `libjpeg-turbo-devel` | AlmaLinux:9 | All versions | 2.0.90-6.el9_1 | | `libjpeg-turbo-utils` | AlmaLinux:9 | All versions | 2.0.90-6.el9_1 | | `turbojpeg` | AlmaLinux:9 | All versions | 2.0.90-6.el9_1 | | `turbojpeg-devel` | AlmaLinux:9 | All versions | 2.0.90-6.el9_1 | | `libjpeg-turbo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-utils` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-utils-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `turbojpeg-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo-utils-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `turbojpeg` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `turbojpeg-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `turbojpeg-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:2.0.90-6.el9_1 | | `libjpeg-turbo` | Rocky Linux:9 | All versions | 0:2.0.90-6.el9_1 | Products: Libjpeg-Turbo Libjpeg-Turbo. ## How do I fix CVE-2021-46822? Upgrade to a fixed version. ## Is CVE-2021-46822 being exploited? There is no known exploitation of CVE-2021-46822 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2020-17541](https://insights.sbomify.com/CVE-2020-17541/): Memory corruption in n/a (high 8.8) - [CVE-2018-20330](https://insights.sbomify.com/CVE-2018-20330/): Integer overflow in n/a (high 8.8) - [CVE-2020-13790](https://insights.sbomify.com/CVE-2020-13790/): Memory corruption in n/a (high 8.1) - [CVE-2023-2804](https://insights.sbomify.com/CVE-2023-2804/): Memory corruption in libjpeg-turbo (medium 6.5) - [CVE-2018-19664](https://insights.sbomify.com/CVE-2018-19664/): Memory corruption in n/a (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-46822 and fix it if it is affected. What it is: CVE-2021-46822 is a medium-severity memory corruption vulnerability in n/a, published on 18 Jun 2022. 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: There is no known exploitation of CVE-2021-46822 in the wild and no public exploit code. 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-2021-46822/ (Markdown: https://insights.sbomify.com/CVE-2021-46822/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-46822 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-46822 - OSV: https://osv.dev/vulnerability/CVE-2021-46822 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-46822/ Summaries are generated and may contain mistakes; the official description above is the record.