Skip to content
Fencer Intel
high 8.8

CVE-2017-12603 json

Out-of-bounds Write in OpenCV

published 9y ago modified last mo. also GHSA-6v6p-p97v-g2p7 , PYSEC-2026-2809 , PYSEC-2026-701 , EUVD-2021-2171

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi opencv-python 3.3.1.11
  • pypi opencv-contrib-python 3.3.1.11
  • opencv Debian 14, Debian 13, Debian 12 3.2.0+dfsg-6

debian advisories DEBIAN-CVE-2017-12603

  • opencv Ubuntu 16.04 LTS 2.4.9.1+dfsg-1.5ubuntu1.1
  • opencv Ubuntu 18.04 LTS 3.2.0+dfsg-4ubuntu0.1

ubuntu advisories UBUNTU-CVE-2017-12603

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2017-12603 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-12603 updated cvss 7.0

opencv: invalid write in the cv::RLByteStream::getBytes function

  • Red Hat Enterprise Linux 6 opencv, opencv-python Red Hat Enterprise Linux 7 opencv, opencv-core, opencv-python
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi opencv-python
<3.3.1.11
3.3.1.11
pypi opencv-contrib-python
<3.3.1.11
3.3.1.11

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.