mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: oss-security@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: CVE request: musl libc 1.1.23 and earlier x87 float stack imbalance
Date: Tue, 6 Aug 2019 11:36:15 -0400	[thread overview]
Message-ID: <20190806153615.GW9017@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190806000539.GQ9017@brightrain.aerifal.cx>

On Mon, Aug 05, 2019 at 08:05:39PM -0400, Rich Felker wrote:
> On Mon, Aug 05, 2019 at 07:27:37PM -0400, Rich Felker wrote:
> > I've discovered a flaw in musl libc's arch-specific math assembly code
> > for i386, whereby at least the log1p function and possibly others
> > return with more than one item on the x87 stack. This can lead to x87
> > stack overflow in the execution of subsequent math code, causing it to
> > incorrectly produce a NAN in place of the actual result. If floating
> > point results are used in flow control, this can lead to runaway wrong
> > code execution. For example, in Python (version 3.6.8 tested), at
> > least one code path of the dtoa function becomes an infinite loop
> > performing what's effectively an unbounded-length memset when entered
> > under such a condition.
> > 
> > This bug is potentially exploitable in software which calls affected
> > math functions with inputs under user control. Impact depends on how
> > the application handles the ABI-violating x87 state; in Python it
> > seems to be limited to producing a crash.
> > 
> > The bug is present in all versions after 0.9.12, up through the
> > current (1.1.23) release. Only 32-bit x86 systems (aka IA32, musl's
> > "i386" arch) are affected. Users of other archs, including x86_64, can
> > safely ignore this issue.
> > 
> > Affected users are advised to apply the following patch:
> > 
> > https://git.musl-libc.org/cgit/musl/patch/?id=f3ed8bfe8a82af1870ddc8696ed4cc1d5aa6b441
> 
> The patch contains an error that was missed for unknown reasons,
> probably failure to rebuild a file. I'm attaching an aggregate patch
> that works. Alternaatively, these two commits can be applied:
> 
> https://git.musl-libc.org/cgit/musl/patch/?id=f3ed8bfe8a82af1870ddc8696ed4cc1d5aa6b441
> https://git.musl-libc.org/cgit/musl/patch/?id=6818c31c9bc4bbad5357f1de14bedf781e5b349e

CVE-2019-14697 has been assigned for this issue.


  reply	other threads:[~2019-08-06 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 23:27 Rich Felker
2019-08-06  0:05 ` Rich Felker
2019-08-06 15:36   ` Rich Felker [this message]
     [not found] ` <20190805232737.GA11260-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2019-08-06  7:16   ` Moritz Muehlenhoff

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=20190806153615.GW9017@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=oss-security@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).