openssh unix dev - Dec 1999 - confusion over RSAref vul w/OpenSS[HL]

Howdy,

  The string  of notices on  BugTraq about  RSAref being vulnerable to
  overflows  has me concerned.  After  trying  to sort through all the
  messages, I  can't figure out  whether I need   to update OpenSSL (a
  check of their website indicates no  new patches), OpenSSH, both, or
  neither.  I am aware there is no known exploit for it yet.

  I could be a bad boy and just run all the code without RSAref, given
  that my  software builds  will   probably outlast the   (ridiculous)
  software  patent, which expires in 10  months.  However,  I figure I
  best pursue a legitimate [legal] solution first.

  What's the deal?

Best,
  "Burned in Boston"

-- 
==============================================================================  
csaia at wtower.com, WTnet IRC Administrator - http://www.wtower.com/~csaia/
    GNU Privacy Guard Public Key information is available at the above URL.
===============================================================================

In message <m3g0xi2yqf.fsf at yakko.wtower.com>, Chris Saia
writes:
>  messages, I  can't figure out  whether I need   to update OpenSSL (a
>  check of their website indicates no  new patches), OpenSSH, both, or
You need to update OpenSSL if you use it with RSAREF2.  I just sent 
the following email to Bugtraq:

Subject: Re: Security Advisory: Buffer overflow in RSAREF2 
From: Niels Provos <provos at citi.umich.edu>
In-Reply-To: Gerardo Richarte, Thu, 02 Dec 1999 16:50:46 -0300
To: Gerardo Richarte <core.lists.bugtraq at CORE-SDI.COM>
Cc: BUGTRAQ at SECURITYFOCUS.COM
Date: Sat, 04 Dec 1999 17:45:20 -0500
Sender: provos at citi.umich.edu

In message <3846CC26.513CE96F at core-sdi.com>, Gerardo Richarte
writes:
>	To make this clear: in combination with the buffer overflow in rsaglue.
>c this makes possible to get
>a remote shell on a machine running sshd AND it also makes possible to use a
r
>everse exploit to gain access on
>clients' machines, using malicious sshd.
I fear that this posting should have been even clearer.
To sum the problem up more clearly:

ssh-1.2.27 (if compiled with RSAREF2) is vulnerable.  Attackers can
obtain a shell on the machine running sshd.  The exploit uses buffer
overflows in the RSAREF2 implementation AND in the rsaglue.c file in
ssh-1.2.27.  I am surprised that there wasnt a bigger outrage on the
mailing list about this, it is quite serious!!!

On the other hand, OpenSSH is not vulnerable to this remote exploit.
Since rsaglue.c was rewritten, OpenSSH does stricter parameter
checking than ssh-1.2.27 and these recent problems in ssh-1.2.27 did
NOT affect OpenSSH.

Nonetheless, OpenSSH users in the USA that use OpenSSL compiled with
RSAREF2 should update their ssl library (since isakmpd or httpd may be
affected), see previous postings on Bugtraq, and
http://www.openbsd.org/errata.html#sslUSA

Another thing is worth mentioning, RSA could use the buffer overflow
in RSAREF2 to scan machines in the USA for RSA license violation.  For
example, sshds that do not use RSAREF2 do will behave differently than
those that do.

Information on OpenSSH can be found at http://www.openssh.com/
Infomration on OpenSSL can be found at http://www.openssl.org/

In message <m3903a2oos.fsf at yakko.wtower.com>, Chris Saia
writes:
>That message is nice and detailed, except it lacks an actual patch.
>The link points to OpenBSD library fixes, but they're not terribly
>useful if you don't run OpenBSD.  :)
The Bugtraq posting contained the relevant patches, have a look
at http://www.securityfocus.com/templates/advisory.html?id=1892.
The patches are only against RSAREF2, nothing else needs fixing.

Niels.