Bug 1511385 (CVE-2017-16671, CVE-2017-16672)

Summary: CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities
Product: [Other] Security Response Reporter: Andrej Nemec <anemec>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: bennie.joubert, itamar, jsmith.fedora, rbryant, redhat
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: asterisk 13.18.1, asterisk 14.7.1, asterisk 15.1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-08 03:30:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1511386, 1511387    
Bug Blocks:    

Description Andrej Nemec 2017-11-09 09:39:08 UTC
Asterisk Project Security Advisory - AST-2017-009

Buffer overflow in pjproject header parsing can cause crash in Asterisk

By carefully crafting invalid values in the Cseq and the Via header port, pjproject’s packet parsing code can create strings larger than the buffer allocated to hold them. This will usually cause Asterisk to crash immediately. The packets do not have to be authenticated.

http://downloads.asterisk.org/pub/security/AST-2017-009.html



Asterisk Project Security Advisory - AST-2017-010 - CVE-2017-16671

Buffer overflow in CDR's set user

No size checking is done when setting the user field for Party B on a CDR. Thus, it is possible for someone to use an arbitrarily large string and write past the end of the user field storage buffer. The earlier AST-2017-001 advisory for the CDR user field overflow was for the Party A buffer.

http://downloads.asterisk.org/pub/security/AST-2017-010.html



Asterisk Project Security Advisory - AST-2017-011 - CVE-2017-16672

Memory/File Descriptor/RTP leak in pjsip session resource

A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. This then leads to file descriptors and RTP ports being leaked as well.

http://downloads.asterisk.org/pub/security/AST-2017-011.html

Comment 1 Andrej Nemec 2017-11-09 09:39:58 UTC
Created asterisk tracking bugs for this issue:

Affects: epel-6 [bug 1511386]
Affects: fedora-all [bug 1511387]

Comment 2 Product Security DevOps Team 2019-06-08 03:30:56 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.