| Summary: | ASTERISK-20369: AMI channelvars option can break manager protocol | ||
| Reporter: | Tim Ringenbach at Asteria Solutions Group (tim_ringenbach) | Labels: | |
| Date Opened: | 2012-09-06 15:34:13 | Date Closed: | |
| Priority: | Major | Regression? | |
| Status: | Open/New | Components: | Core/ManagerInterface |
| Versions: | 11.0.0-beta1 13.18.4 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | The manager.conf channelvars setting can break the manager protocol in two ways. Because it uses a header of ChanVariable(channelname), if you do something like this cli command "channel originate Local/700):@all_calls/n application MusicOnHold" then you get headers that look like this: ChanVariable(Local/700):@all_calls-08ee;2): SIPCALLID= with extra colons and parentheses. (I think there's some more natural ways to get channels with colons in them, don't SIP channel names sometimes include the port number? I used the local channel example to prove that matching parens isn't good enough.) Since SIP can dial arbitrary urls, if the dialplan involves Dial(Local/{$EXTEN}@context), someone without CLI access could trigger this bug. The other way, is you can set channelvars to something like SHELL(ls) and then it throws a bunch of new lines into the manager. | ||
| Comments: | |||