[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141008092305.GC6890@pc.thejh.net>
Date: Wed, 8 Oct 2014 11:23:05 +0200
From: Jann Horn <jann@...jh.net>
To: oss-security@...ts.openwall.com
Cc: Damien Miller <djm@...drot.org>
Subject: Re: openssh on linux rce in sftp-only mode
On Wed, Oct 08, 2014 at 11:07:59AM +0200, Hanno Böck wrote:
> This seems CVE-worthy:
> http://seclists.org/fulldisclosure/2014/Oct/35
>
> Quote:
> "OpenSSH lets you grant SFTP access to users without allowing full
> command execution using "ForceCommand internal-sftp". However, if you
> misconfigure the server and don't use ChrootDirectory, the user will be
> able to access all parts of the filesystem that he has access to -
> including procfs. On modern Linux kernels (>=2.6.39, I
> think), /proc/self/maps reveals the memory layout and /proc/self/mem
> lets you write to arbitrary memory positions. Combine those and you get
> easy RCE."
>
> It involves a number of issues coming together, however in the end it
> is an RCE with a legit configuration.
I reported this to the OpenSSH developers, and although they included my
patch as a mitigation, they did not treat it as a vuln in OpenSSH.
I believe that treating this as a hardening patch makes sense. The SFTP
server behaves exactly as documented, it allows access to the whole
filesystem. And on Linux, that happens to equal write access to the
process RAM, so you should never give that access to someone who
shouldn't be able to run arbitrary code.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
