# CVE-2020-17541: Memory corruption in n/a > A stack-based buffer overflow in Libjpeg-turbo allows remote attackers to execute arbitrary code or cause denial of service via a malformed JPEG file. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 1 Jun 2021 - **Updated:** 4 Aug 2024 - **Also known as:** ALSA-2021:4288, AZL-6637, DEBIAN-CVE-2020-17541, GHSA-vhxw-68wq-v5j9, JLSEC-2025-179, RHSA-2021:4288, RLSA-2021:4288, SUSE-SU-2021:1957-1, SUSE-SU-2021:1958-1, UBUNTU-CVE-2020-17541, openSUSE-SU-2021:0892-1, openSUSE-SU-2021:1958-1 ## What is CVE-2020-17541? CVE-2020-17541 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2020-17541? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libjpeg-turbo` | AlmaLinux:8 | All versions | 1.5.3-12.el8 | | `libjpeg-turbo-devel` | AlmaLinux:8 | All versions | 1.5.3-12.el8 | | `libjpeg-turbo-utils` | AlmaLinux:8 | All versions | 1.5.3-12.el8 | | `turbojpeg` | AlmaLinux:8 | All versions | 1.5.3-12.el8 | | `turbojpeg-devel` | AlmaLinux:8 | All versions | 1.5.3-12.el8 | | `libjpeg-turbo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `turbojpeg` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `turbojpeg-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo-utils-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.5.3-12.el8 | | `turbojpeg-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.5.3-12.el8 | | `turbojpeg-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo` | Rocky Linux:8 | All versions | 0:1.5.3-12.el8 | | `libjpeg-turbo` | SUSE:Linux Enterprise Micro 5.0 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 1.5.3-5.18.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 1.5.3-5.18.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP3 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Package Hub 15 SP2 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Package Hub 15 SP3 | All versions | 1.5.3-5.18.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.5.3-31.25.1 | | `libjpeg-turbo` | openSUSE:Leap 15.2 | All versions | 1.5.3-lp152.8.6.1 | | `libjpeg62-turbo` | openSUSE:Leap 15.2 | All versions | 1.5.3-lp152.8.6.1 | | `libjpeg-turbo` | openSUSE:Leap 15.3 | All versions | 1.5.3-5.18.1 | | `libjpeg62-turbo` | openSUSE:Leap 15.3 | All versions | 1.5.3-5.18.1 | Products: Libjpeg-Turbo Libjpeg-Turbo. ## How do I fix CVE-2020-17541? Apply the vendor's patch. ## Is CVE-2020-17541 being exploited? There is no known exploitation of CVE-2020-17541 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [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) - [CVE-2017-15232](https://insights.sbomify.com/CVE-2017-15232/): Null dereference in n/a (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-17541 and fix it if it is affected. What it is: CVE-2020-17541 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-17541 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-2020-17541/ (Markdown: https://insights.sbomify.com/CVE-2020-17541/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-17541 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-17541 - OSV: https://osv.dev/vulnerability/CVE-2020-17541 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-17541/ Summaries are generated and may contain mistakes; the official description above is the record.