× Few antiviral products inadequately detect 3proxy as Trojan.Daemonize, Backdoor.Daemonize, etc and many detect 3proxy as a PUA (potentially unwanted program). It may cause browser warning on download page. 3proxy is not trojan or backdoor and contains no functionality except described in documentation. Clear explanation of this fact is given, for example, in Microsoft's article.

Topic:                    Sambar Server all versions password
Author:                   3APA3A <[email protected]>
SECURITY.NNOV advisories: http://www.security.nnov.ru/advisories
Vulnerable:               All Sambar versions up to 5.0 beta
Impact:                   passwords  can be decoded back to
Vendor URL:               http://www.sambar.com
Released:                 24 July 2001
Credits:                  mam0nt[GiN], [email protected]


Sambar  is  widely  used  Web/Proxy/Mail  server for Windows
(there  are  both free and commercial "Pro" versions).


Sambar  documentation  states  there  is  no  way  to repair
forgotten password. It's not true, because by default server
uses  blowfish  with  statically compiled key to encrypt all
password.  Blowfish  uses  symmetric  key, it means with the
same  key passwords can be easily decrypted. I don't believe
authors  didn't  knew  that  because  they  coded decryption
function  too.  Sambar  authors are aware about this problem
(in  fact  it's  known  since  at  least  1999  according to
mam0nt  page http://www.secure.f2s.com/texts/found_bug.php -
in Russian). I  wonder why  authors  do  not  document  this


I  was  too  lazy  to  discover  blowfish key. I didn't even
checked is it blowfish or DES (in fact I didn't even started
debugger.  I  did  everything  in text editor :)). Instead I
wrote  small  program  which  "cracks"  sacrypt.exe  to load
decryption  function  of  blowfish instead of encryption one
from DLL by changing string argument of GetProcAddress().
For more details see sadecrypt.c from sadecrypt.zip


--(quoting "Sambar Server Support" <[email protected]>)

Many thanks.  Several folks have pointed out this
vulnerability recently.  I used the two-way encryption
algorithm intentionally to allow the password to be
viewed/modified.  I have the option (config.ini) of 
substituting UNIX crypt() for the two way hash I use 
(blowfish) and will recommend folks switch to that.

appreciate it.
--(quoting "Sambar Server Support" <[email protected]>)--