Security readout for executives and security teams
Plain-English summary
OpenCV before 4.1.1 can read outside allocated memory when processing certain small images in its DIS optical flow code. For businesses, the main concern is applications that process untrusted images or video frames using affected OpenCV functionality. Public sources do not show active exploitation.
Executive priority
Treat this as a targeted dependency remediation item, not an emergency, unless affected OpenCV processing is exposed to untrusted media at scale. Prioritize services that automatically process uploaded images or video.
Technical view
The flaw is an out-of-bounds heap read in dis_flow.cpp. calc()/ocl_calc() assume coarsest_scale is at least finest_scale, which can fail for small images, causing out-of-bounds reads from Ux and Uy arrays. The bundled sources identify OpenCV before 4.1.1 and reference an upstream issue and commit.
Likely exposure
Exposure is most likely in software embedding OpenCV before 4.1.1 and using DIS optical flow paths on images or frames that attackers can influence. General OpenCV presence alone is not enough to confirm reachability.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. The issue and commit indicate public disclosure and upstream remediation, but exploitability impact is not fully characterized in the provided sources.
Researcher notes
The evidence is specific to OpenCV DIS optical flow handling of small images. Provided data lacks CVSS, CWE, affected CPEs, and detailed impact beyond out-of-bounds heap read, so validation should focus on version and code-path reachability.
Mitigation direction
- Upgrade affected OpenCV deployments to 4.1.1 or later where feasible.
- Check distribution or vendor packages for backported OpenCV fixes.
- Restrict untrusted image processing through affected DIS optical flow functionality.
- Add input size validation for workflows that use OpenCV optical flow.
- Prioritize internet-facing or automated media-processing services first.
Validation and detection
- Inventory OpenCV versions in applications, containers, servers, and bundled libraries.
- Identify code paths using DIS optical flow or dis_flow.cpp functionality.
- Confirm whether small, untrusted images can reach those code paths.
- Review SBOMs and dependency manifests for OpenCV versions before 4.1.1.
- Verify remediation by checking deployed OpenCV version or vendor patch metadata.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-19624 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/opencv/opencv/issues/14554CVE reference · x_refsource_MISC
- https://github.com/opencv/opencv/commit/d1615ba11a93062b1429fce9f0f638d1572d3418CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.