Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround for malicious/broken SIP-clients #52

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lemenkov
Copy link

Hello All!

Some nasty SIP-clients sends only \n instead of \r\n (malicious SIP scanners). We shouldn't crash
on these packets.

Actually I'm not sure about how we should handle this. RFC 3261 states clearly that the only allowed line terminator is CRLF, however previous RFC 2543 does allows line endings with CR, LF, and CRLF. Also some people advise allowing CRLF, CR, and LF as a line delimiters when parsing incoming SIP packets (see http://www.networksorcery.com/enp/protocol/sip.htm).

What other thinks about this? Is it worth fixing at all?

Some nasty SIP-clients sends only \n instead of \r\n. We shouldn't crash
on these packets.

Signed-off-by: Peter Lemenkov <[email protected]>
@kalta
Copy link
Member

kalta commented Oct 21, 2015

Maybe we could add a global config options, and accept that optionally if you activate it.
Global options are compiled and very fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants