# CVE-2020-0452: Integer overflow in Android > An integer overflow in the libexif library allows remote code execution when processing malicious image data, affecting Android and other systems using this library. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed - **Fix available:** Yes - **Published:** 10 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** A-159625731, ALSA-2020:5393, ASB-A-159625731, DEBIAN-CVE-2020-0452, DLA-2439-1, DSA-4786-1, GHSA-xrf9-3q75-637f, MGASA-2020-0426, OESA-2024-1078, RHSA-2020:5393, RHSA-2020:5394, RHSA-2020:5395, RHSA-2020:5396, RHSA-2020:5402, RLSA-2020:5393, UBUNTU-CVE-2020-0452, USN-4624-1 ## What is CVE-2020-0452? CVE-2020-0452 is a critical vulnerability in Fedoraproject Fedora, published on 10 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In exif_entry_get_value of exif-entry.c, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution if a third party app used this library to process remote image data with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-11 Android-8.0Android ID: A-159625731 Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2020-0452? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libexif` | AlmaLinux:8 | All versions | 0.6.22-5.el8_3 | | `libexif-devel` | AlmaLinux:8 | All versions | 0.6.22-5.el8_3 | | `libexif` | Red Hat:enterprise_linux:7::client | All versions | 0:0.6.22-2.el7_9 | | `libexif-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.6.22-2.el7_9 | | `libexif-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.6.22-2.el7_9 | | `libexif-doc` | Red Hat:enterprise_linux:7::client | All versions | 0:0.6.22-2.el7_9 | | `libexif` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.6.22-2.el7_9 | | `libexif-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.6.22-2.el7_9 | | `libexif-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.6.22-2.el7_9 | | `libexif-doc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.6.22-2.el7_9 | | `libexif` | Red Hat:enterprise_linux:7::server | All versions | 0:0.6.22-2.el7_9 | | `libexif-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.6.22-2.el7_9 | | `libexif-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.6.22-2.el7_9 | | `libexif-doc` | Red Hat:enterprise_linux:7::server | All versions | 0:0.6.22-2.el7_9 | | `libexif` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.6.22-2.el7_9 | | `libexif-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.6.22-2.el7_9 | | `libexif-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.6.22-2.el7_9 | | `libexif-doc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.6.22-2.el7_9 | | `libexif` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.6.22-5.el8_3 | | `libexif-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.6.22-5.el8_3 | | `libexif-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.6.22-5.el8_3 | | `libexif-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.6.22-5.el8_3 | | `libexif-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.6.22-5.el8_3 | | `libexif-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.6.22-5.el8_3 | | `libexif` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:0.6.21-18.el8_0 | | `libexif-debuginfo` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:0.6.21-18.el8_0 | | `libexif-debugsource` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:0.6.21-18.el8_0 | | `libexif` | Red Hat:rhel_eus:8.1::appstream | All versions | 0:0.6.21-18.el8_1 | | `libexif-debuginfo` | Red Hat:rhel_eus:8.1::appstream | All versions | 0:0.6.21-18.el8_1 | | `libexif-debugsource` | Red Hat:rhel_eus:8.1::appstream | All versions | 0:0.6.21-18.el8_1 | | `libexif-debuginfo` | Red Hat:rhel_eus:8.1::crb | All versions | 0:0.6.21-18.el8_1 | | `libexif-debugsource` | Red Hat:rhel_eus:8.1::crb | All versions | 0:0.6.21-18.el8_1 | | `libexif-devel` | Red Hat:rhel_eus:8.1::crb | All versions | 0:0.6.21-18.el8_1 | | `libexif` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.6.21-18.el8_2 | | `libexif-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.6.21-18.el8_2 | | `libexif-debugsource` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.6.21-18.el8_2 | | `libexif-debuginfo` | Red Hat:rhel_eus:8.2::crb | All versions | 0:0.6.21-18.el8_2 | | `libexif-debugsource` | Red Hat:rhel_eus:8.2::crb | All versions | 0:0.6.21-18.el8_2 | | `libexif-devel` | Red Hat:rhel_eus:8.2::crb | All versions | 0:0.6.21-18.el8_2 | | `libexif` | Rocky Linux:8 | All versions | 0:0.6.22-5.el8_3 | Products: Fedoraproject Fedora, Google Android. ## How do I fix CVE-2020-0452? Apply the vendor's patch. ## Is CVE-2020-0452 being exploited? There is no known exploitation of CVE-2020-0452 in the wild and no public exploit code. Public exploit code: - https://github.com/ShaikUsaf/external_libexif_AOSP10_CVE-2020-0452 (github_poc): https://github.com/ShaikUsaf/external_libexif_AOSP10_CVE-2020-0452 ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-0452 and fix it if it is affected. What it is: CVE-2020-0452 is a critical vulnerability in Fedoraproject Fedora, published on 10 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-0452 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-0452/ (Markdown: https://insights.sbomify.com/CVE-2020-0452/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0452 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0452 - OSV: https://osv.dev/vulnerability/CVE-2020-0452 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-0452/ Summaries are generated and may contain mistakes; the official description above is the record.