Reported by Tony Lewis) - - --- Fix a longstanding issue with MFC-R2 configuration that - prevented users - (Closes issue ASTERISK-21117.
Neither App Meetme Nor App Confbridge Is Configured In Asterisk Conferencing Paging And Other Functionality Will Not Work Properly Code Would IncorrectlyIf a - payload length of zero was received the code would incorrectly attempt to - resize to zero.
This operation would succeed and end up freeing the memory but - be treated as a failure. A bug has been discovered where the address family of incoming - packets is only compared to the IP address family of the first entry in the - list of access control rules. If the source IP address for an incoming - packet is not of the same address as the first ACL entry, that packet - bypasses all ACL rules. AST-2014-018: Permission Escalation through DB dialplan function - - The DB dialplan function when executed from an external protocol, such as AMI, - could result in a privilege escalation. Users with a lower class authorization - in AMI can access the internal Asterisk database without the required SYSTEM - class authorization. In addition, the release of 11.6-cert8 and 11.14.1 resolves the following - security vulnerability: - - AST-2014-014: High call load with ConfBridge can result in resource exhaustion - - The ConfBridge application uses an internal bridging API to implement - conference bridges. This internal API uses a state model for channels within - the conference bridge and transitions between states as different things - occur. Unload load it is possible for some state transitions to be delayed - causing the channel to transition from being hung up to waiting for media. Additionally, the AMI - ConfbridgeStartRecord action has options that would allow modification of the - underlying system, and does not require SYSTEM class authorization in AMI. Finally, the release of 12.7.1 and 13.0.1 resolves the following security - vulnerabilities: - - AST-2014-013: Unauthorized access in the presence of ACLs in the PJSIP stack - - The Asterisk module respjsip provides the ability to configure ACLs that may - be used to reject SIP requests from various hosts. However, the module - currently fails to create and apply the ACLs defined in its configuration - file on initial module load. AST-2014-015: Remote crash vulnerability in PJSIP channel driver - - The chanpjsip channel driver uses a queue approach for relating to SIP - sessions. There exists a race condition where actions may be queued to answer - a session or send ringing after a SIP session has been terminated using a - CANCEL request. The code will incorrectly assume that the SIP session is still - active and attempt to send the SIP response. The PJSIP library does not - expect the SIP session to be in the disconnected state when sending the - response and asserts. AST-2014-016: Remote crash vulnerability in PJSIP channel driver - - When handling an INVITE with Replaces message the respjsiprefer module - incorrectly assumes that it will be operating on a channel that has just been - created. If the INVITE with Replaces message is sent in-dialog after a session - has been established this assumption will be incorrect. It is a Long Term - Support (LTS) release, similar to Asterisk 11. For more information about - support time lines for Asterisk releases, see the Asterisk versions page: - - - For important information regarding upgrading to Asterisk 13, please see the - Asterisk wiki: - - - - A short list of new features includes: - - Asterisk security events are now provided via AMI, allowing end users to - monitor their Asterisk system in real time for security related issues. Both AMI and ARI now allow external systems to control the state of a mailbox. Using AMI actions or ARI resources, external systems can programmatically - trigger Message Waiting Indicators (MWI) on subscribed phones. This is of - particular use to those who want to build their own VoiceMail application - using ARI. ARI now supports the receptiontransmission of out of call text messages using - any supported channel driverprotocol stack through ARI. This includes defining lists of presence state, - mailbox state, or lists of presence statemailbox state; managing - subscriptions to lists; and batched delivery of NOTIFY requests to - subscribers. The PJSIP stack can now be used as a means of distributing device state or - mailbox state via PUBLISH requests to other Asterisk instances. Asterisk does not require system class authorization for a manager - user to use the MixMonitor action, so any manager user who is permitted to use - manager commands can potentially execute shell commands as the user executing - the Asterisk process. Neither App Meetme Nor App Confbridge Is Configured In Asterisk Conferencing Paging And Other Functionality Will Not Work Properly Drivers Pubsub FrameworkAdditionally, the release of 12.3.1 resolves the following issues: - - AST-2014-005: Remote Crash in PJSIP Channel Drivers PublishSubscribe - Framework - - A remotely exploitable crash vulnerability exists in the PJSIP channel - drivers pubsub framework. If an attempt is made to unsubscribe when not - currently subscribed and the endpoints subminexpiry is set to zero, - Asterisk tries to create an expiration timer with zero seconds, which is not - allowed, so an assertion raised. AST-2014-008: Denial of Service in PJSIP Channel Driver Subscriptions - - When a SIP transaction timeout caused a subscription to be terminated, the - action taken by Asterisk was guaranteed to deadlock the thread on which SIP - requests are serviced. Reported by Jonathan White) - - --- appqueue: Fix CLI queue remove member queuelog entry. Closes issue ASTERISK-21826. Reported by Oscar Esteve) - - --- chansip: Do not increment the SDP version between 183 and 200 - responses. Closes issue ASTERISK-21204. Reported by NITESH BANSAL) - - --- chansip: Allow a sip peer to accept both AVP and AVPF calls - (Closes issue ASTERISK-22005. Asterisk - now marks certain individual dialplan functions as dangerous, which will - inhibit their execution from external sources. A dangerous function is one which results in a privilege escalation. Reported by Chris Gentle) - - --- Let Queue wrap up time influence member availability - (Closes issue ASTERISK-22189.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |