CVE-2017-12862

Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV

In modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2017-12862 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.1.11); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2017-12862? CVE-2017-12862 is a high-severity out-of-bounds write vulnerability in opencv-python (pip), affecting versions <= 3.3.0.9. It is fixed in 3.3.1.11. A write operation targets a memory location beyond the intended buffer boundary.
2. How severe is CVE-2017-12862? CVE-2017-12862 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2017-12862?
   • opencv-python (pip) (versions <= 3.3.0.9)
   • opencv-contrib-python (pip) (versions <= 3.3.0.9)
4. Is there a fix for CVE-2017-12862? Yes. CVE-2017-12862 is fixed in 3.3.1.11. Upgrade to this version or later.
5. Is CVE-2017-12862 exploitable, and should I be worried? Whether CVE-2017-12862 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-12862 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-12862?
   • Upgrade opencv-python to 3.3.1.11 or later
   • Upgrade opencv-contrib-python to 3.3.1.11 or later

Other vulnerabilities in opencv-python