public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thierry Carrez <koon@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com,  full-disclosure@lists.netsys.com,
	 security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200410-28 ] rssh: Format string vulnerability
Date: Wed, 27 Oct 2004 17:02:09 +0200	[thread overview]
Message-ID: <417FB871.6090300@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2690 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200410-28
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: High
     Title: rssh: Format string vulnerability
      Date: October 27, 2004
      Bugs: #66988
        ID: 200410-28

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

Synopsis
========

rssh is vulnerable to a format string vulnerability that allows
arbitrary execution of code with the rights of the connected user,
thereby bypassing rssh restrictions.

Background
==========

rssh is a restricted shell, allowing only a few commands like scp or
sftp. It is often used as a complement to OpenSSH to provide limited
access to users.

Affected packages
=================

    -------------------------------------------------------------------
     Package          /  Vulnerable  /                      Unaffected
    -------------------------------------------------------------------
  1  app-shells/rssh       < 2.2.2                            >= 2.2.2

Description
===========

Florian Schilhabel from the Gentoo Linux Security Audit Team found a
format string vulnerability in rssh syslogging of failed commands.

Impact
======

Using a malicious command, it may be possible for a remote
authenticated user to execute arbitrary code on the target machine with
user rights, effectively bypassing any restriction of rssh.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All rssh users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=app-shells/rssh-2.2.2"

References
==========

  [ 1 ] rssh security announcement
        http://www.pizzashack.org/rssh/security.shtml

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

  http://security.gentoo.org/glsa/glsa-200410-28.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.

License
=======

Copyright 2004 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/1.0


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-10-27 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=417FB871.6090300@gentoo.org \
    --to=koon@gentoo.org \
    --cc=bugtraq@securityfocus.com \
    --cc=full-disclosure@lists.netsys.com \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security-alerts@linuxsecurity.com \
    /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