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

[Ralf Kubis (JIRA)]

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

Ralf Kubis commented on ASTERISK-29024:
---------------------------------------

Kevin Harvell,

due to a very limited time budget also on my side, and the fair amount of debugging time I've already invested, I sadly have to inform You that I'm unable to further participate in resolving this issue.
In fact, I strongly believe that the extra effort to prepare an adequate pull request will be for me, a guy with a very limited unterstanding of Your framework and programming techniques, ... challenging.
Even If I would try this, someone with a deep understanding of the code base will receive the task to review and, in case, fix my code - hopefully. I hardly see any benefit but just more overhead.

Thanks again and fingers crossed

> pjsip: 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)