Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14748 > unrolled thread
| Started by | Eduardo Bustamante <dualbus@gmail.com> |
|---|---|
| First post | 2018-10-30 18:19 -0700 |
| Last post | 2018-10-30 18:19 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Use-After-Free in Bash Eduardo Bustamante <dualbus@gmail.com> - 2018-10-30 18:19 -0700
| From | Eduardo Bustamante <dualbus@gmail.com> |
|---|---|
| Date | 2018-10-30 18:19 -0700 |
| Subject | Re: Use-After-Free in Bash |
| Message-ID | <mailman.3143.1540948790.1284.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web