A flaw was found in libwebp in versions before 1.0.1. A use-after-free was found due to a thread being killed too early. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
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=1956843 | issue tracking release notes patch third party advisory |
| https://lists.debian.org/debian-lts-announce/2021/06/msg00005.html | third party advisory mailing list |
| https://lists.debian.org/debian-lts-announce/2021/06/msg00006.html | third party advisory mailing list |
| https://www.debian.org/security/2021/dsa-4930 | third party advisory vendor advisory |
| https://support.apple.com/kb/HT212601 | third party advisory |
| http://seclists.org/fulldisclosure/2021/Jul/54 | third party advisory mailing list |
| https://security.netapp.com/advisory/ntap-20211112-0001/ | third party advisory |