CVE-2017-12603 Out-of-bounds Write in OpenCV
An attacker can trigger an invalid write in OpenCV via a crafted image file, potentially leading to code execution or application crash.
- 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
What is CVE-2017-12603?
CVE-2017-12603 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 7 Aug 2017. 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
OpenCV (Open Source Computer Vision Library) through 3.3 has an invalid write in the cv::RLByteStream::getBytes function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 2-opencv-heapoverflow-fseek test case.
Weakness: CWE-787
Which versions are affected by CVE-2017-12603?
6 open source packages ship an affected version, including opencv-contrib-python and opencv-python. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
opencv-contrib-python PyPI | All versions | 3.3.1.11 |
opencv-contrib-python PyPI | All versions | 3.3.1.11 |
opencv-contrib-python PyPI | All versions | 3.3.1.11 |
opencv-python PyPI | All versions | 3.3.1.11 |
opencv-python PyPI | All versions | 3.3.1.11 |
opencv-python PyPI | All versions | 3.3.1.11 |
Products include Debian Debian Linux, Opencv Opencv.
How do I fix CVE-2017-12603?
Upgrade opencv-contrib-python to 3.3.1.11 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-12603 being exploited?
There is no known exploitation of CVE-2017-12603 in the wild and no public exploit code.
Other vulnerabilities in Debian Debian Linux
Sources
Also known as DEBIAN-CVE-2017-12603, GHSA-6v6p-p97v-g2p7, PYSEC-2026-2809, PYSEC-2026-701, UBUNTU-CVE-2017-12603.