public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferry Meyndert <m0rpheus@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] OpenSSH Security Fix.
Date: Thu, 7 Mar 2002 18:50:32 +0100	[thread overview]
Message-ID: <20020307185032.5359836c.m0rpheus@gentoo.org> (raw)
In-Reply-To: <3C87C7E7.9040407@cdavies.org>

Its allready fixed in gentoo here is a copy of the anouncement send to the anouncement list.
- --------------------------------------------------------------------------
GENTOO LINUX SECURITY ANNOUNCEMENT 
- --------------------------------------------------------------------------

PACKAGE        :openssh
SUMMARY        :vulnerable to a off-by-one error in the channel code
DATE           :2002-04-7 18:02:00

- --------------------------------------------------------------------------

OVERVIEW

 
 A bug exists in the channel code of OpenSSH versions 2.0 - 3.0.2
 Users with an existing user account can abuse this bug to
 gain root privileges. Exploitability without an existing
 user account has not been proven but is not considered
 impossible. A malicious ssh server could also use this bug 
 to exploit a connecting vulnerable client.


DETAIL

 http://www.pine.nl/advisories/pine-cert-20020301.txt


SOLUTION

 
 It is recommended that all openssh users apply the update

 Portage Auto:

 emerge rsync
 emerge update
 emerge update --world


 Portage by hand:

 emerge rsync
 emerge net-misc/openssh

 Manually:

 Download the new openssh package here and follow in file instructions:
 ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-3.1p1.tar.gz

- --------------------------------------------------------------------------
Ferry Meyndert
m0rpheus@gentoo.org
- --------------------------------------------------------------------------


On Thu, 07 Mar 2002 20:04:55 +0000
Chris Davies <c.davies@cdavies.org> wrote:

> Hi,
> 
> I haven't seen anything in bugs or this list about this, so here is the 
> news:
> CERT have issued an advisory about OpenSSH, the bug in question enables 
> existing users to gain root privelidges.
> The advisory is here: http://www.pine.nl/advisories/pine-cert-20020301.txt
> The fix is to upgrade to the latest OpenSSH (3.1p1) ASAP.
> May I politely suggest that a new ebuild be constructed post-haste? :)
> Anyway, for those at risk, I have constructed an emergency ebuild and 
> digest file, so you may upgrade immediately.
> The files can be found here: http://www.cdavies.org/gentoo/
> 
> Put the digest file in /usr/portage/net-misc/openssh/files and the 
> ebuild in /usr/portage/net-misc/openssh and rerun emerge openssh.
> 
> If anyone thinks it is worthwhile, I will also post this message to the 
> gentoo users list, but at present I'm not going to do that.
> Thanks,
> C.Davies
> (c.davies@cdavies.org)
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev


  reply	other threads:[~2002-03-07 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 18:18 [gentoo-dev] Install report, bugs, questions & suggestions Sylvain OBEGI
2002-03-06 20:36 ` Maciek Borowka
2002-03-07  0:20   ` Sylvain OBEGI
2002-03-07  0:23     ` Sylvain OBEGI
2002-03-07 20:04       ` [gentoo-dev] OpenSSH Security Fix Chris Davies
2002-03-07 17:50         ` Ferry Meyndert [this message]
2002-03-07 21:26           ` Chris Davies

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020307185032.5359836c.m0rpheus@gentoo.org \
    --to=m0rpheus@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox