Bug 1327434 (AST-2016-004) - asterisk: crash via long contact URIs in REGISTER
Summary: asterisk: crash via long contact URIs in REGISTER
Keywords:
Status: CLOSED UPSTREAM
Alias: AST-2016-004
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1327435 1327436
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 07:25 UTC by Andrej Nemec
Modified: 2021-02-17 04:03 UTC (History)
5 users (show)

Fixed In Version: asterisk 13.8.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 02:50:45 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Andrej Nemec 2016-04-15 07:25:04 UTC 
Asterisk may crash when processing an incoming REGISTER      
request if that REGISTER contains a Contact header with a    
lengthy URI.                                                 
                                                                              
This crash will only happen for requests that pass           
authentication. Unauthenticated REGISTER requests will not   
result in a crash occurring.                                 
                                                                              
This vulnerability only affects Asterisk when using PJSIP    
as its SIP stack. The chan_sip module does not have this     
problem.

External references:

http://downloads.asterisk.org/pub/security/AST-2016-004.html
Comment 1 Andrej Nemec 2016-04-15 07:25:38 UTC 
Created asterisk tracking bugs for this issue:

Affects: fedora-all [bug 1327435]
Affects: epel-6 [bug 1327436]
Comment 2 Product Security DevOps Team 2019-06-08 02:50:45 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.