summaryrefslogtreecommitdiff
blob: e87f7485d76b47c69d3d975290b15e2033f33628 (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
54
55
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201911-01">
  <title>OpenSSH: Integer overflow</title>
  <synopsis>An integer overflow in OpenSSH might allow an attacker to execute
    arbitrary code.
  </synopsis>
  <product type="ebuild">openssh</product>
  <announced>2019-11-07</announced>
  <revised count="1">2019-11-07</revised>
  <bug>697046</bug>
  <access>remote</access>
  <affected>
    <package name="net-misc/openssh" auto="yes" arch="*">
      <unaffected range="ge">8.0_p1-r4</unaffected>
      <vulnerable range="ge">8.0_p1-r2</vulnerable>
    </package>
  </affected>
  <background>
    <p>OpenSSH is a complete SSH protocol implementation that includes SFTP
      client and server support.
    </p>
  </background>
  <description>
    <p>OpenSSH, when built with “xmss” USE flag enabled, has a
      pre-authentication integer overflow if a client or server is configured
      to use a crafted XMSS key.
    </p>
    
    <p>NOTE: This USE flag is disabled by default!</p>
  </description>
  <impact type="normal">
    <p>A remote attacker could connect to a vulnerable OpenSSH server using a
      special crafted XMSS key possibly resulting in execution of arbitrary
      code with the privileges of the process or a Denial of Service condition.
    </p>
  </impact>
  <workaround>
    <p>Disable XMSS key type.</p>
  </workaround>
  <resolution>
    <p>All OpenSSH users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose
      "&gt;=net-misc/openssh/openssh-8.0_p1-r4"
    </code>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2019-16905">CVE-2019-16905</uri>
  </references>
  <metadata tag="requester" timestamp="2019-10-26T14:48:28Z">whissi</metadata>
  <metadata tag="submitter" timestamp="2019-11-07T19:01:23Z">whissi</metadata>
</glsa>