GHSA-jggw-2q6g-c3m6 CVE-2019-19624 PYSEC-2026-2800 PYSEC-2026-2824 PYSEC-2026-2839 PYSEC-2026-723
Out-of-bounds Read in OpenCV
Medium
PyPI
- Severity
- 6.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.76%
- Chance of exploitation in the next 30 days. Higher than 77.95% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-125 Out-of-bounds Read
- Fix
- Available
- 4 packages have a fixed version
Description
An out-of-bounds read was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.0.25). Specifically, variable coarsest_scale is assumed to be greater than or equal to finest_scale within the calc()/ocl_calc() functions in dis_flow.cpp. However, this is not true when dealing with small images, leading to an out-of-bounds read of the heap-allocated arrays Ux and Uy.
Affected versions
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| opencv-contrib-python | < 4.1.0.25 |
4.1.0.25 |
| opencv-contrib-python-headless | < 4.1.0.25 |
4.1.0.25 |
| opencv-contrib-python-headless | < 4.1.0.25 |
4.1.0.25 |
| opencv-python | < 4.1.0.25 |
4.1.0.25 |
| opencv-python | < 4.1.0.25 |
4.1.0.25 |
| opencv-python-headless | < 4.1.0.25 |
4.1.0.25 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
opencv-contrib-python PyPI → 4.1.0.25
- pip
pip install --upgrade "opencv-contrib-python>=4.1.0.25"- poetry
poetry add "opencv-contrib-python>=4.1.0.25"- uv
uv add "opencv-contrib-python>=4.1.0.25"
opencv-contrib-python-headless PyPI → 4.1.0.25
- pip
pip install --upgrade "opencv-contrib-python-headless>=4.1.0.25"- poetry
poetry add "opencv-contrib-python-headless>=4.1.0.25"- uv
uv add "opencv-contrib-python-headless>=4.1.0.25"
opencv-python PyPI → 4.1.0.25
- pip
pip install --upgrade "opencv-python>=4.1.0.25"- poetry
poetry add "opencv-python>=4.1.0.25"- uv
uv add "opencv-python>=4.1.0.25"
opencv-python-headless PyPI → 4.1.0.25
- pip
pip install --upgrade "opencv-python-headless>=4.1.0.25"- poetry
poetry add "opencv-python-headless>=4.1.0.25"- uv
uv add "opencv-python-headless>=4.1.0.25"
Severity breakdown
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
Weakness
CWE-125: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How to prevent it
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.
- Architecture and Design: Use a language that provides appropriate memory abstractions.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| PYSEC-2023-183 opencv-python versions before v4.8.1.78 bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863. | High Known exploited | Also affects opencv-python |
| PYSEC-2023-181 opencv-contrib-python versions before v4.8.1.78 bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863. | High Known exploited | Also affects opencv-contrib-python |
| GHSA-qr4w-53vh-m672 opencv-python bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863 | High | Also affects opencv-python |
| GHSA-cxjf-x6jp-p7mc opencv-contrib-python bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863 | High | Also affects opencv-contrib-python |
| GHSA-9g8h-pjm4-q92p Out-of-bounds Write in OpenCV. | Medium | Also affects opencv-contrib-python |
| GHSA-q799-q27x-vp7w Out-of-bounds Write in OpenCV | High | Also affects opencv-contrib-python |
| GHSA-m6vm-8g8v-xfjh Out-of-bounds Write in OpenCV | High | Also affects opencv-contrib-python |
| GHSA-8849-5h85-98qw Out-of-bounds Write in OpenCV | High | Also affects opencv-contrib-python |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor