# CVE-2023-44398: Out-of-bounds write in exiv2 > An out-of-bounds write in Exiv2 allows attackers to execute arbitrary code by tricking users into processing a crafted image 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:** 6 Nov 2023 - **Updated:** 26 Feb 2025 - **Also known as:** AZL-31939, AZL-36940, CLEANSTART-2024-EU98453, GHSA-hrw9-ggg3-3r4r, PYSEC-2023-233, openSUSE-SU-2024:13403-1 ## What is CVE-2023-44398? CVE-2023-44398 is a high-severity memory corruption vulnerability in Exiv2 Exiv2, published on 6 Nov 2023. 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 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. An out-of-bounds write was found in Exiv2 version v0.28.0. The vulnerable function, `BmffImage::brotliUncompress`, is new in v0.28.0, so earlier versions of Exiv2 are _not_ affected. The out-of-bounds write is triggered when Exiv2 is used to read the metadata of a crafted image file. An attacker could potentially exploit the vulnerability to gain code execution, if they can trick the victim into running Exiv2 on a crafted image file. This bug is fixed in version v0.28.1. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2023-44398? 1 open source package ship an affected version, including exiv2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `exiv2` | PyPI | All versions | None | | `exiv2` | openSUSE:Tumbleweed | All versions | 0.28.1-1.1 | Products: Exiv2 Exiv2. ## How do I fix CVE-2023-44398? Upgrade to a fixed version. ## Is CVE-2023-44398 being exploited? There is no known exploitation of CVE-2023-44398 in the wild and no public exploit code. ## Other vulnerabilities in Exiv2 Exiv2 - [CVE-2019-9143](https://insights.sbomify.com/CVE-2019-9143/): Denial of service in n/a (high 8.8) - [CVE-2019-9144](https://insights.sbomify.com/CVE-2019-9144/): Denial of service in n/a (high 8.8) - [CVE-2018-14046](https://insights.sbomify.com/CVE-2018-14046/): Memory corruption in n/a (high 8.8) - [CVE-2017-12955](https://insights.sbomify.com/CVE-2017-12955/): Memory corruption in n/a (high 8.8) - [CVE-2018-14338](https://insights.sbomify.com/CVE-2018-14338/): Memory corruption in n/a (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-44398 and fix it if it is affected. What it is: CVE-2023-44398 is a high-severity memory corruption vulnerability in Exiv2 Exiv2, published on 6 Nov 2023. 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-2023-44398 in the wild and no public exploit code. Affected packages and fixed versions: - exiv2 (PyPI): affected all versions; no fix listed 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-2023-44398/ (Markdown: https://insights.sbomify.com/CVE-2023-44398/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-44398 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-44398 - OSV: https://osv.dev/vulnerability/CVE-2023-44398 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-44398/ Summaries are generated and may contain mistakes; the official description above is the record.