[Fwd: Radware Security Advisory - Yate 1.1.0 Denial of Service Vulnerability]

[Mikael Magnusson]

Yate 1.0.0-1.dfsg-2 in Debian stable and 1.1.0-1.dfsg-1 in testing and 
unstable contains a Denial of Service Vulnerability.

The patch applied by upstream to CVS and released in yate 1.2.0 can be 
found as an attachment. The patch applies successfully to both yate 
1.0.0 and yate 1.1.0.

yate 1.2.0-1.dfsg-1 is available in pkg-voip svn. It has been tested on 
x86, but not built by Buildserver.NET yet.

Thanks,
Mikael

-------- Original Message --------
Subject: Radware Security Advisory - Yate 1.1.0 Denial of Service 
Vulnerability
Date: Tue, 1 May 2007 20:52:51 +0300
From: no-reply at radware.com
To: bugtraq at securityfocus.com, full-disclosure at lists.grok.org.uk, 
vulnwatch at vulnwatch.org, voipsec at voipsa.org
Newsgroups: 
gmane.comp.security.bugtraq,gmane.comp.security.full-disclosure,gmane.comp.voip.security.voipsa

Yate 1.1.0 Denial of Service Vulnerability



Risk: Medium


Background:


Yate (Yet Another Telephony Engine) is a production-ready 
next-generation telephony engine.

More information about this application could be obtained from the 
following site:

http://yate.null.ro/


Description:


The SIP channel module of Yate contains a denial of service 
vulnerability, introduced by a
null pointer dereference, which could be provoked by having the SIP 
module process SIP messages
containing the "Call-Info" header, without the "purpose" parameter as 
part of its value.

The flaw can be seen in the following source code snippet:

File:    yate/modules/ysipchan.cpp
Lines:   1585 - 1594

1:    const SIPHeaderLine* hl = 
m_tr->initialMessage()->getHeader("Call-Info");
2:    if (hl) {
3:        const NamedString* type = hl->getParam("purpose");
4:        if (!type || *type == "info")
5:            mp type->addParam("caller_info_uri",*type);
6:        else if (*type == "icon")
7:            m->addParam("caller_icon_uri",*type);
8:        else if (*type == "card")
9:            m->addParam("caller_card_uri",*type);
10:   }

Once the "Call-Info" header is found in the SIP message (line 1), there 
is an attempt to extract
the "purpose" parameter (line 3).
Afterwards, a decision is made to set the "caller_info_uri" parameter 
(line 5) to the value of the
"Call-Info" header, though due to a programming error, instead of 
assigning the parameter with the
header value, it is being assigned with the value of the "purpose" 
parameter - allowing for a null
pointer dereference, when the call to getParam() (line 3) returns 0 in 
case of a missing "purpose" parameter.


Analysis:

Exploiting this vulnerability could allow for denial of service to Yate 
and disruption of the VoIP
infrastructure.

By default no authentication is required to exploit this vulnerability, 
allowing for spoofed UDP SIP
messages to trigger the flaw.


Radware DefensePro IPS Solution:

Radware DefensePro customers are protected against this vulnerability 
since the release of signature
database version 0006.0030.00 by RWID's 7334,7338 and 7342.


Detection:

Radware Security Operations Center has confirmed the existence of this 
vulnerability in Yate 1.1.0.
Previous versions are also suspected to be vulnerable.


Workaround:

A workaround for this vulnerability is currently not known.


Vendor Response:

The maintainers of Yate addressed this vulnerability with the release of 
Yate 1.2.0.


CVE Information:

The Common Vulnerabilities and Exposures (CVE) project has assigned the 
name CVE-2007-1693 to this issue.


Disclosure Timeline:

March 25, 2007  -       Initial vendor notification
March 25, 2007  -       Initial vendor response
March 26, 2007  -       Vendor fixes flaw in CVS
April 16, 2007  -       Vendor releases fixed version
April 30, 2007  -       Attack database release
May 1, 2007     -       Advisory release


Credit:

Yuri Gushin, Radware Security Operations Center


Legal Information:

Disclaimer: The information in the advisory is believed to be accurate 
at the time of publishing
based on currently available information. Use of the information 
constitutes acceptance for use in
an AS IS condition. There are no warranties with regard to this 
information. Neither the author
nor the publisher accepts any liability for any direct, indirect, or 
consequential loss or damage
arising from use of, or reliance on, this information.



-------------- next part --------------
Mon Mar 26 13:00:29 CEST 2007  paulc
  * [yate @ 2007-03-26 11:00:29 by paulc]
  Fixed Call-Info parsing bug found by Yuri Gushin from Radware Inc.
diff -rN -u old-upstream/modules/ysipchan.cpp new-upstream/modules/ysipchan.cpp
--- old-upstream/modules/ysipchan.cpp	2007-05-02 19:23:11.000000000 +0200
+++ new-upstream/modules/ysipchan.cpp	2007-05-02 19:23:12.000000000 +0200
@@ -1656,11 +1656,11 @@
     if (hl) {
 	const NamedString* type = hl->getParam("purpose");
 	if (!type || *type == "info")
-	    m->addParam("caller_info_uri",*type);
+	    m->addParam("caller_info_uri",*hl);
 	else if (*type == "icon")
-	    m->addParam("caller_icon_uri",*type);
+	    m->addParam("caller_icon_uri",*hl);
 	else if (*type == "card")
-	    m->addParam("caller_card_uri",*type);
+	    m->addParam("caller_card_uri",*hl);
     }
 
     if (line) {