In our production system we caught a pcap that had a To: SIP header separated from the From: header by LF character (0x0A) instead of the usual CRLF (0x0D0A) combination. This caused this library to end up in a sort-of an infinite loop that caused our service's CPU to be pegged, essentially rendering our service useless.
W're not sure LF separators are allowed, but in order to fix this issue we decided to update the SipParser to consider LF to be a valid separator of SIP headers. This PR shows the changes that we made.
In our production system we caught a pcap that had a
To:
SIP header separated from theFrom:
header byLF
character (0x0A) instead of the usual CRLF (0x0D0A) combination. This caused this library to end up in a sort-of an infinite loop that caused our service's CPU to be pegged, essentially rendering our service useless.W're not sure
LF
separators are allowed, but in order to fix this issue we decided to update the SipParser to considerLF
to be a valid separator of SIP headers. This PR shows the changes that we made.