A memory leak was found in the way SIPcrack 0.2 handled...
High severity
Unreviewed
Published
May 13, 2022
to the GitHub Advisory Database
•
Updated Jan 27, 2023
Description
Published by the National Vulnerability Database
Jul 26, 2017
Published to the GitHub Advisory Database
May 13, 2022
Last updated
Jan 27, 2023
A memory leak was found in the way SIPcrack 0.2 handled processing of SIP traffic, because a lines array was mismanaged. A remote attacker could potentially use this flaw to crash long-running sipdump network sniffing sessions.
References