[asterisk-bugs] [JIRA] (ASTERISK-30257) res_pjsip: IP addresses get butchered

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-30257:
--------------------------------------

    Assignee: N A
      Status: Waiting for Feedback  (was: Triage)

I'm not really sure what you're expecting to be done with this report. The PJSIP parser failed validation on an incoming packet and it was dropped at the PJSIP level. It never reached the Asterisk code, 'nor would it have gotten caught by any ACL.

Afterwards the ast_sockaddr_resolve message occurred from a different thread, so a different SIP message could have come in, but none are in this issue report so I don't know. You also mention an ACL, but don't explain how you came to that conclusion.

I can't do anything with this report as it is. It needs much more information, including the SIP requests that caused it.

> res_pjsip: IP addresses get butchered
> -------------------------------------
>
>                 Key: ASTERISK-30257
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30257
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 18.14.0
>            Reporter: N A
>            Assignee: N A
>
> This happened a few times today:
> Note how the 2nd octet gets butchered into nonsense, causing an ACL failure.
> {noformat}
>  [2022-10-02 14:50:43] ERROR[13793]: pjproject: <?>:            sip_transport.c Error processing 100 bytes packet from UDP 173.56.227.13:18599 : PJSIP syntax error exception when parsing 'Request Line' header on line 1 col 1:
> [2022-10-02 14:50:43]        > ▒
> [2022-10-02 14:50:43] ERROR[12886]: netsock2.c:303 ast_sockaddr_resolve: getaddrinfo("173.566.227.13", "(null)", ...): Name or service not known
> {noformat}



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