[asterisk-bugs] [JIRA] (ASTERISK-29024) pjsip: Route Header in Cancel request incorrectly set
Flole Systems (JIRA)
noreply at issues.asterisk.org
Tue Oct 6 08:37:36 CDT 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-29024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252336#comment-252336 ]
Flole Systems commented on ASTERISK-29024:
------------------------------------------
I saw something similar today with an ACK to a "407 Proxy Authentication Required" aswell (not sure if the cause is the same though).
Wireshark shows in the ACK:
{noformat}
...
Route: <sip:\000\000\000\000\000\000\000\000\000\000\000\000\000\000:5060;lr>
...
{noformat}
I have never seen that before and about a minute later on a similar 407 the ACK-Route was containing the proper IP, no Idea what went wrong there but it seems to be some kind of Route-Header-Corruption aswell.
> 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)
More information about the asterisk-bugs
mailing list