summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-202003-13.xml
blob: 4eabdcd70b9b13aecaca32a8883eedc7f9d6f1c5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="202003-13">
  <title>musl: x87 floating-point stack adjustment imbalance</title>
  <synopsis>An x87 stack handling error in musl might allow an attacker to have
    an application dependent impact.
  </synopsis>
  <product type="ebuild">musl</product>
  <announced>2020-03-14</announced>
  <revised count="2">2020-03-15</revised>
  <bug>711276</bug>
  <access>local, remote</access>
  <affected>
    <package name="sys-libs/musl" auto="yes" arch="*">
      <unaffected range="ge">1.1.24</unaffected>
      <vulnerable range="lt">1.1.24</vulnerable>
    </package>
  </affected>
  <background>
    <p>musl is an implementation of the C standard library built on top of the
      Linux system call API, including interfaces defined in the base language
      standard, POSIX, and widely agreed-upon extensions.
    </p>
  </background>
  <description>
    <p>A flaw in musl libc’s arch-specific math assembly code for i386 was
      found which can lead to x87 stack overflow in the execution of subsequent
      math code.
    </p>
  </description>
  <impact type="normal">
    <p>Impact depends on how the application built against musl libc handles
      the ABI-violating x87 state.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All musl users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=sys-libs/musl-1.1.24"
    </code>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2019-14697">CVE-2019-14697</uri>
  </references>
  <metadata tag="requester" timestamp="2020-03-03T20:43:59Z">whissi</metadata>
  <metadata tag="submitter" timestamp="2020-03-15T00:52:05Z">whissi</metadata>
</glsa>