# CVE-2019-5063: Out-of-bounds Write in OpenCV > A heap buffer overflow in OpenCV allows attackers to execute arbitrary code by providing a specially crafted XML file. - **Severity:** High 8.8 (`CVSS:3.0/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:** 3 Jan 2020 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-5063, GHSA-m6vm-8g8v-xfjh, PYSEC-2026-2801, PYSEC-2026-2826, PYSEC-2026-2840, PYSEC-2026-724 ## What is CVE-2019-5063? CVE-2019-5063 is a high-severity memory corruption vulnerability in Oracle Application Testing Suite, published on 3 Jan 2020. 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 An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV 4.1.0. A specially crafted XML file can cause a buffer overflow, resulting in multiple heap corruptions and potential code execution. An attacker can provide a specially crafted file to trigger this vulnerability. Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2019-5063? 12 open source packages ship an affected version, including opencv-contrib-python, opencv-contrib-python-headless and opencv-python. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `opencv-contrib-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-contrib-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-contrib-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.0.25 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.0.25 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.0.25 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.0.25 | None | Products: Opencv Opencv, Oracle Application Testing Suite, Oracle Big Data Spatial and Graph, Oracle Enterprise Manager Base Platform. ## How do I fix CVE-2019-5063? Upgrade to a fixed version. ## Is CVE-2019-5063 being exploited? There is no known exploitation of CVE-2019-5063 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Application Testing Suite - [CVE-2019-5064](https://insights.sbomify.com/CVE-2019-5064/): Out-of-bounds Write in OpenCV (high 8.8) - [CVE-2019-14491](https://insights.sbomify.com/CVE-2019-14491/): Out-of-bounds Read in OpenCV (high 8.2) - [CVE-2019-14492](https://insights.sbomify.com/CVE-2019-14492/): Out-of-bounds Read and Out-of-bounds Write in OpenCV (high 7.5) - [CVE-2018-7712](https://insights.sbomify.com/CVE-2018-7712/): Denial of service in n/a (high 7.5) - [CVE-2018-7713](https://insights.sbomify.com/CVE-2018-7713/): Denial of service in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-5063 and fix it if it is affected. What it is: CVE-2019-5063 is a high-severity memory corruption vulnerability in Oracle Application Testing Suite, published on 3 Jan 2020. 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-5063 in the wild and no public exploit code. Affected packages and fixed versions: - opencv-contrib-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-contrib-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-contrib-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.0.25; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.0.25; 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-2019-5063/ (Markdown: https://insights.sbomify.com/CVE-2019-5063/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5063 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5063 - OSV: https://osv.dev/vulnerability/CVE-2019-5063 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-5063/ Summaries are generated and may contain mistakes; the official description above is the record.