full-disclosure - Re: Cisco Phone 7940 remote DOS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <FB5575C1-8056-4F23-9C78-7DF07CAF4C4C@cisco.com>
Date: Sat, 8 Dec 2007 02:29:50 -0500
From: Clay Seaman-Kossmey <ckossmey@...co.com>
To: full-disclosure@...ts.grok.org.uk
Cc: "psirt \(mailer list\)" <psirt@...co.com>
Subject: Re: Cisco Phone 7940 remote DOS

Hello -

This is Cisco's response to the message posted by Radu State to full- 
disclosure on Wednesday Dec 5 2007.  Cisco greatly appreciates the  
opportunity to work with researchers on security vulnerabilities, and  
welcomes the opportunity to review and assist in product reports.

Cisco confirms that there is an issue whereby a crafted sequence of  
SIP messages may cause the phone to enter a state where no calls can  
be placed from, or received by a Cisco IP phone running Session  
Initiation Protocol (SIP) software.  Once the crafted SIP messages  
stop, the device will return to normal service.  This issue is  
tracked by Cisco bug ID CSCsl63427.  Registered customers will be  
able to view additional information here

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do? 
method=fetchBugDetails&bugId=CSCsl63427

This issue is not seen when the SIP phone is registered to a Cisco  
Unified Communications Manager (CUCM) server, as additional checking  
is done that would prevent the attack.

Cisco was unable to reproduce the device restart as described by Mr.  
State.

This issue has been assigned the Common Vulnerabilities and Exposures  
identifier of CVE-2007-5583.

As a possible mitigation for this issue, Cisco recommends, as a best  
practice, that voice infrastructure devices are kept on separate
networks from data devices.  In this case, the crafted packets may be  
prevented from reaching the
voice devices.

Regards,

Clay Seaman-Kossmeyer
Cisco PSIRT
Content of type "text/html" skipped

Download attachment "PGP.sig" of type "application/pgp-signature" (187 bytes)

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/