An issue was discovered in Irssi before 1.0.4. While updating the internal nick list, Irssi could incorrectly use the GHashTable interface and free the nick while updating it. This would then result in use-after-free conditions on each access of the hash table.
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://www.debian.org/security/2017/dsa-4016 | vendor advisory |
https://irssi.org/security/irssi_sa_2017_07.txt | patch vendor advisory |
https://github.com/irssi/irssi/commit/5e26325317c72a04c1610ad952974e206384d291 | issue tracking third party advisory patch |