# CVE-2019-17402: Denial of service in n/a > Attackers can cause a crash in the Exiv2 library by providing a malformed CRW image file, leading to a denial of service. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Oct 2019 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2019-17402, ALSA-2021:1758, AZL-7204, CLEANSTART-2024-BZ69967, DEBIAN-CVE-2019-17402, DLA-2019-1, GHSA-xhv3-q5hx-88ww, RHSA-2020:4030, RHSA-2021:1758, RLSA-2021:1758, UBUNTU-CVE-2019-17402, USN-4159-1 ## What is CVE-2019-17402? CVE-2019-17402 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 9 Oct 2019. 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 Exiv2 0.27.2 allows attackers to trigger a crash in Exiv2::getULong in types.cpp when called from Exiv2::Internal::CiffDirectory::readDirectory in crwimage_int.cpp, because there is no validation of the relationship of the total size to the offset and size. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2019-17402? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `exiv2-devel` | AlmaLinux:8 | All versions | 0.27.3-2.el8 | | `exiv2-doc` | AlmaLinux:8 | All versions | 0.27.3-2.el8 | | `exiv2` | Red Hat:enterprise_linux:7::client | All versions | 0:0.27.0-3.el7_8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.27.0-3.el7_8 | | `exiv2-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.27.0-3.el7_8 | | `exiv2-doc` | Red Hat:enterprise_linux:7::client | All versions | 0:0.27.0-3.el7_8 | | `exiv2-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:0.27.0-3.el7_8 | | `exiv2` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.27.0-3.el7_8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.27.0-3.el7_8 | | `exiv2-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.27.0-3.el7_8 | | `exiv2-doc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.27.0-3.el7_8 | | `exiv2-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.27.0-3.el7_8 | | `exiv2` | Red Hat:enterprise_linux:7::server | All versions | 0:0.27.0-3.el7_8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.27.0-3.el7_8 | | `exiv2-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.27.0-3.el7_8 | | `exiv2-doc` | Red Hat:enterprise_linux:7::server | All versions | 0:0.27.0-3.el7_8 | | `exiv2-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:0.27.0-3.el7_8 | | `exiv2` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.27.0-3.el7_8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.27.0-3.el7_8 | | `exiv2-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.27.0-3.el7_8 | | `exiv2-doc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.27.0-3.el7_8 | | `exiv2-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.27.0-3.el7_8 | | `exiv2` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.27.3-2.el8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.27.3-2.el8 | | `exiv2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.27.3-2.el8 | | `exiv2-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.27.3-2.el8 | | `exiv2-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.27.3-2.el8 | | `exiv2-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.27.3-2.el8 | | `exiv2-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.27.3-2.el8 | | `exiv2-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.27.3-2.el8 | | `exiv2-doc` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.27.3-2.el8 | | `exiv2-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.27.3-2.el8 | | `exiv2` | Rocky Linux:8 | All versions | 0:0.27.3-2.el8 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Exiv2 Exiv2. ## How do I fix CVE-2019-17402? Upgrade to a fixed version. ## Is CVE-2019-17402 being exploited? There is no known exploitation of CVE-2019-17402 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-17402 and fix it if it is affected. What it is: CVE-2019-17402 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 9 Oct 2019. 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-2019-17402 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. 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-2019-17402/ (Markdown: https://insights.sbomify.com/CVE-2019-17402/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-17402 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-17402 - OSV: https://osv.dev/vulnerability/CVE-2019-17402 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-17402/ Summaries are generated and may contain mistakes; the official description above is the record.