Skip to content
Fencer Intel
high 7.5

CVE-2019-14493 json

NULL Pointer Dereference in OpenCV.

published 7y ago modified last mo. also GHSA-3448-vrgh-85xr , PYSEC-2026-2795 , PYSEC-2026-2806 , PYSEC-2026-2834 , PYSEC-2026-718 , EUVD-2021-2144

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

Summary

An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp.

Patch / fix

  • pypi opencv-python 4.1.1.26
  • pypi opencv-python-headless 4.1.1.26
  • pypi opencv-contrib-python 4.1.1.26
  • pypi opencv-contrib-python-headless 4.1.1.26
  • opencv opencv 4.1.1
  • opencv Debian 14, Debian 13, Debian 12 4.1.2+dfsg-3

debian advisories DEBIAN-CVE-2019-14493

  • opencv Ubuntu Pro 14.04 LTS 2.4.8+dfsg1-2ubuntu1.2+esm1
  • opencv Ubuntu Pro 16.04 LTS 2.4.9.1+dfsg-1.5ubuntu1.1+esm1
  • opencv Ubuntu Pro 18.04 LTS 3.2.0+dfsg-4ubuntu0.1+esm4

ubuntu advisories UBUNTU-CVE-2019-14493

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-2019-14493 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-2019-14493 updated cvss 7.5

opencv: NULL pointer dereference in function cv::XMLParser::parse() in persistence_xml.cpp leading to DoS

  • Red Hat Enterprise Linux 6 opencv, opencv-python Red Hat Enterprise Linux 7 opencv, opencv-core, opencv-python Red Hat Enterprise Linux 8 opencv, opencv-core, opencv-contrib, python3-opencv
    not affected: vulnerable code not present

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

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

Exploits and checks

  • github.com https://github.com/opencv/opencv/issues/15127 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi opencv-python
<4.1.1.26
4.1.1.26
pypi opencv-python-headless
<4.1.1.26
4.1.1.26
pypi opencv-contrib-python
<4.1.1.26
4.1.1.26
pypi opencv-contrib-python-headless
<4.1.1.26
4.1.1.26

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.