[asterisk-bugs] [JIRA] (ASTERISK-29024) Route Header in Cancel request incorrectly set

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251640#comment-251640 ] 

Kevin Harwell commented on ASTERISK-29024:
------------------------------------------

I'm not seeing this behavior. I'm doing the following:

Using a similar configuration to that given in the previous comment I originate a call from Asterisk to that endpoint. While the "called" endpoint is being rung I then hangup the call (in this case via the Asterisk CLI). A SIP CANCEL is then sent from Asterisk to the endpoint.

Does that sound about right?

Could you please enable Asterisk debug logging [1] with sip trace, and attach the log here.

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

> Route Header in Cancel request incorrectly set
> ----------------------------------------------
>
>                 Key: ASTERISK-29024
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29024
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 17.6.0
>            Reporter: Flole Systems
>            Assignee: Unassigned
>
> When I initiate a call using PJSIP and Cancel the call while it's still ringing the Route-Header seems to be sent incorrectly. It looks like it's a pointer to a memory region that got overwritten. I saw internal IP Addresses in there aswell as some other stuff like "Route: <sip:}". The "Route: <sip:" is always set properly, just the part after the sip is never set correctly and also the closing ">" is always missing.
> As the memory region that it reads from can't be controlled it might happen that confidential data like a password is exposed over this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)