# CVE-2019-9423: Out-of-bounds Write in OpenCV > A missing bounds check in OpenCV's libpng usage allows local attackers to escalate privileges on Android devices without user interaction. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 27 Sep 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-8849-5h85-98qw, PYSEC-2026-2796, PYSEC-2026-2811, PYSEC-2026-2835, PYSEC-2026-719, UBUNTU-CVE-2019-9423 ## What is CVE-2019-9423? CVE-2019-9423 is a high-severity memory corruption vulnerability in Google Android, published on 27 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In opencv calls that use libpng, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges required. User interaction is not required for exploitation. Product: AndroidVersions: Android-10Android ID: A-110986616 Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-9423? 12 open source packages ship an affected version, including opencv-contrib-python, opencv-contrib-python-headless and opencv-python. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `opencv-contrib-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-contrib-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-contrib-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.1.26 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.1.26 | None | | `opencv-contrib-python-headless` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.1.26 | None | | `opencv-python-headless` | PyPI | All versions to 4.1.1.26 | None | Products: Google Android. ## How do I fix CVE-2019-9423? No fix has been published for CVE-2019-9423 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-9423 being exploited? There is no known exploitation of CVE-2019-9423 in the wild and no public exploit code. ## Other vulnerabilities in Google Android - [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild) - [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild) - [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild) - [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild) - [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-9423 and fix it if it is affected. What it is: CVE-2019-9423 is a high-severity memory corruption vulnerability in Google Android, published on 27 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-9423 in the wild and no public exploit code. Affected packages and fixed versions: - opencv-contrib-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-contrib-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-contrib-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-contrib-python-headless (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.1.26; no fix listed - opencv-python-headless (PyPI): affected all versions up to 4.1.1.26; 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-9423/ (Markdown: https://insights.sbomify.com/CVE-2019-9423/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9423 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9423 - OSV: https://osv.dev/vulnerability/CVE-2019-9423 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-9423/ Summaries are generated and may contain mistakes; the official description above is the record.