[asterisk-bugs] [JIRA] (ASTERISK-23322) Unable to use SIP INVITE authentication with type=peer and device name mismatch with username

[Igor Nikolaev (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Nikolaev updated ASTERISK-23322:
-------------------------------------

    Attachment: asterisk-chan_sip-inbound-invite-auth.patch

This patch fix described issue.

If you specify parameter "fromuser=..." in sip.conf device entry for a peer, incoming INVITE checked with fromuser name instead of device name. Therefore, device name may be either with authname and INVITE auth still checked (you don't need specify "insecure=invite")
                
> Unable to use SIP INVITE authentication with type=peer and device name mismatch with username
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23322
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23322
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_sip/Security Framework
>    Affects Versions: 11.2.0, 11.2.1, 11.2.2, 11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.6.0, 11.6.1, 11.7.0
>            Reporter: Igor Nikolaev
>            Severity: Trivial
>         Attachments: asterisk-chan_sip-inbound-invite-auth.patch
>
>
> Scenario:
> sip.conf
> [devicename]
> type=peer
> fromuser=authuser
> secret=...
> In this case if devicename not equal authuser you need add statement "insecure=invite" for receiving incoming calls. But this INVITEs is not authenticated by receiving system. It's security hole.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira