Title: Re: Witango-Talk: upgrade issues.
Maybe Phil can reply here. I thought that version fixed the problem and the issue was with size now and was intentional

( From a previous post by Phil:

>
> Now on to cookies other the reserved mentioned above
> Tested
> Ver.        Cookie Name            Max Length
> 5.0.1.062     <Cookie name Here>    unknown - I just did one with 2600 chars

Witango Server 5.0.1.062 is now limited to a 3K buffer size for setting
cookies.  Anything larger is truncated and discarded.  So the maximum size
of a cookie is a 3K and a buffer over run is no longer possible.

> 4.05.020    <Cookie name Here>     approx. 500-1024 char*
>
> * When testing version 4 I was at times able to place numbers greater than
> 1024, but other times it would crash the server.

What Ben has demonstrated is how easy it is to bring down the T2K server
with this vulnerability.  The Witango 5 server prior to and including
version 5.0.1.061 also had this cookie buffer overrun but were not as prone
to crashing due to the changes to the threading model.  We also suspect T3
will have the same issue but have not tested it.

What happens in a buffer overrun is that the server tries to copy the large
cookie to its memory and writes over memory which it has not allocated to
store the cookie.  If the cookie string is carefully crafted there is a
possibility that the bytes that over run the buffer may be able to be
executed.  In most cases it will crash the server or a thread.


on 11/16/03 19:13, Stefan Gonick at [EMAIL PROTECTED] wrote:

I was referring to version 5.0.1.062 as having the cookie problem.
It has not been fixed in a officially released version since then.

Stefan

At 06:49 PM 11/16/2003, you wrote:
I thought the cookies issue was fixed in the last server version.

Not sure what you mean by number 2 can you expand a little.

Dan

on 11/16/03 18:33, Stefan Gonick at [EMAIL PROTECTED] wrote:

At 12:04 AM 11/15/2003, you wrote:
I in the process of upgrading my t2k application to witango5 and am encountering a couple issues;
 
(1)    my cookies don’t appear to be assigning correctly, are there config file settings that could affect this?
(2)    I created some simple test tafs from scratch and the files are outputting in HTML, ie., <B>test</b> is not showing as “test” in bold but appearing as <B>test</b>
 
Any guidance is much appreciated.
 
------------------------------------
Bradley J. Robertson



If you are using Witango 5 version ending with .062, then there
is a known issue with persistent cookies not working. The only
fix is to either use an earlier version of Witango 5 or upgrade to
the next maintenance version when it comes out, hopefully soon.

Stefan

========================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com < <http://www.databasewebworks.com/> http://www.databasewebworks.com/> <http://www.databasewebworks.com/>  

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf




--
Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Mobile: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com


    "When you are born, you cry and those who love you rejoice.  And if you
live your life as you should, when you die, you rejoice and those who
love you cry."
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to