<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
.MsoChpDefault
{}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
-->
</style>
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’m a new subscriber working on security cameras.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’m experiencing an RTSP server crash in the DESCRIBE phase which I have traced to the function ServerMediaSession::generateSDPDescription().</p>
<p class="MsoNormal">In this function, I think the sdpLength is being calculated based on the length of the session-level description.</p>
<p class="MsoNormal">However, at the end of the function, when the media-level description lines are appended, I believe that the previous memory allocation is being exceeded.</p>
<p class="MsoNormal">I found that the server would crash when I was returning a large media-level description due to a large “a=fmtp:96...” string.</p>
<p class="MsoNormal">Temporarily increasing sdpLength by 400 bytes fixed the problem.</p>
<p class="MsoNormal">When the media-level description was a smaller length, the server did not crash but I guess there was still possible data corruption occurring unless you are building in some allowance for the maximum media-level description when calculating
sdpLength.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Found on version 2013.11.15.</p>
<p class="MsoNormal">I am currently upgrading to latest version but by code inspection I guess this is still likely to occur.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">If you need any further info, please let me know.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">Mike Brimer</p>
<p class="MsoNormal">Oncam Grandeye</p>
<p class="MsoNormal"> </p>
</div>
This communication is for the exclusive use of the addressee and may contain information that is private and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication and
its attachments is strictly prohibited. If you have received this information in error please contact the sender and delete the communication from your system. Any views or opinions presented are solely those of the author and do not necessarily represent
those of Oncam Grandeye unless specifically stated.
<br><br>
<P align=center><FONT style="BACKGROUND-COLOR: #ffffff">This message has been scanned for malware by Websense. </FONT><A href="http://www.websense.com/"><FONT style="BACKGROUND-COLOR: #ffffff" color=#000000>www.websense.com</FONT></A></P>
</body>
</html>