Bug 832625 (CVE-2012-3553) - CVE-2012-3553 asterisk: skinny channel driver remote crash vulnerability
Summary: CVE-2012-3553 asterisk: skinny channel driver remote crash vulnerability
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2012-3553
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: 832626
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-16 01:16 UTC by Vincent Danen
Modified: 2021-10-19 21:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-19 21:54:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2012-06-16 01:16:29 UTC
AST-2012-008 previously dealt with a denial of service attack exploitable in the Skinny channel driver that occurred when certain messages are sent after a previously registered station sends an Off Hook message. Unresolved in that patch is an issue in the Asterisk 10 releases, wherein, if a Station Key Pad Button Message is processed after an Off Hook message, the channel driver will inappropriately dereference a Null pointer.

Similar to AST-2012-008, a remote attacker with a valid SCCP ID can can use this vulnerability by closing a connection to the Asterisk server when a station is in the "Off Hook" call state and crash the server.

This only affects version 10, and is fixed in 10.5.1.

References:

http://downloads.digium.com/pub/security/AST-2012-009.html
https://issues.asterisk.org/jira/browse/ASTERISK-19905
http://downloads.asterisk.org/pub/security/AST-2012-009-10.diff

Comment 1 Vincent Danen 2012-06-16 01:18:05 UTC
Created asterisk tracking bugs for this issue

Affects: fedora-17 [bug 832626]

Comment 2 Fedora Update System 2012-06-26 00:39:00 UTC
asterisk-10.5.1-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.