Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14748

Re: Use-After-Free in Bash

From Eduardo Bustamante <dualbus@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Use-After-Free in Bash
Date 2018-10-30 18:19 -0700
Message-ID <mailman.3143.1540948790.1284.bug-bash@gnu.org> (permalink)
References <CALQDDJ90PG3c957jWTp_XE6-h_-1OdjTpeGhFso=iYtTBfyoNg@mail.gmail.com>

Show all headers | View raw


On Tue, Oct 30, 2018 at 1:03 PM Corbin Souffrant
<corbin.souffrant@gmail.com> wrote:
(...)
> I found a reproducible use-after-free in every version of Bash from
> 4.4-5.0beta, that could potentially be used to escape restricted mode. I
> say potentially, because I can get it to crash in restricted mode, but I
> haven't gone through the effort of attempting to heap spray to overwrite
> function pointers.

Disclaimer: I'm not a maintainer.

Did you check the `devel' branch in the git repository?

I don't think the restricted mode is really advertised as a powerful
security feature, so IMO you should be able to report it here. If
you're worried though, you can always email Chet Ramey directly.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Use-After-Free in Bash Eduardo Bustamante <dualbus@gmail.com> - 2018-10-30 18:19 -0700

csiph-web