A use-after-free flaw has been discovered in libcomps before version 0.1.10 in the way ObjMRTrees are merged. An attacker, who is able to make an application read a crafted comps XML file, may be able to crash the application or execute malicious code.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3817 | issue tracking exploit vendor advisory |
| https://github.com/rpm-software-management/libcomps/issues/41 | issue tracking exploit third party advisory |
| https://github.com/rpm-software-management/libcomps/commit/e3a5d056633677959ad924a51758876d415e7046 | third party advisory patch |
| https://access.redhat.com/errata/RHSA-2019:3583 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:3898 | vendor advisory |