Bug 1160255 - (CVE-2019-5063) VUL-0: CVE-2019-5063, CVE-2019-5064: opencv: heap buffer overflow via a specially crafted XML file in the data structure persistence functionality
(CVE-2019-5063)
VUL-0: CVE-2019-5063, CVE-2019-5064: opencv: heap buffer overflow via a spe...
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Security
Current
Other Other
: P3 - Medium : Major (vote)
: Current
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/250339/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-01-07 13:36 UTC by Alexandros Toptsoglou
Modified: 2020-07-03 11:41 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandros Toptsoglou 2020-01-07 13:36:36 UTC
CVE-2019-5063

An exploitable heap buffer overflow vulnerability exists in the data structure
persistence functionality of OpenCV 4.1.0. A specially crafted XML file can
cause a buffer overflow, resulting in multiple heap corruptions and potential
code execution. An attacker can provide a specially crafted file to trigger this
vulnerability.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-5063
http://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-5063.html
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5063
https://talosintelligence.com/vulnerability_reports/TALOS-2019-0852
Comment 1 Alexandros Toptsoglou 2020-01-07 13:41:35 UTC
Versions of 3.X and older are not affected. 
Only TW is affected. The fix is available at [0]. 
Please upgrade to 4.2.0 [1]. 

[0] https://github.com/opencv/opencv/pull/15868
[1] https://github.com/opencv/opencv/releases/tag/4.2.0
Comment 2 Scott Reeves 2020-06-16 17:32:14 UTC
(In reply to Alexandros Toptsoglou from comment #1)
> Versions of 3.X and older are not affected. 
> Only TW is affected. The fix is available at [0]. 
> Please upgrade to 4.2.0 [1]. 

TW is now at 4.2.0 so this should be done.
Comment 3 Alexandros Toptsoglou 2020-07-03 11:41:06 UTC
Done