An issue was discovered in Irssi before 1.0.7 and 1.1.x before 1.1.1. There is a use-after-free when SASL messages are received in an unexpected order.
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/2018/dsa-4162 | third party advisory vendor advisory |
| https://irssi.org/security/irssi_sa_2018_02.txt | mitigation vendor advisory |
| http://openwall.com/lists/oss-security/2018/02/15/1 | third party advisory mailing list |
| https://usn.ubuntu.com/3590-1/ | third party advisory vendor advisory |