metadata/glsa/glsa-201710-09.xml


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
56
57
58
59
60
61
62
63
64
65
66

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201710-09">
  <title>PCRE2: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in PCRE2, the worst of
    which may allow remote attackers to execute arbitrary code.
  </synopsis>
  <product type="ebuild">libpcre2</product>
  <announced>2017-10-08</announced>
  <revised count="1">2017-10-08</revised>
  <bug>614050</bug>
  <bug>617942</bug>
  <bug>617944</bug>
  <access>remote</access>
  <affected>
    <package name="dev-libs/libpcre2" auto="yes" arch="*">
      <unaffected range="ge">10.30</unaffected>
      <vulnerable range="lt">10.30</vulnerable>
    </package>
  </affected>
  <background>
    <p>PCRE2 is a project based on PCRE (Perl Compatible Regular Expressions)
      which has a new and revised API.
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in PCRE2. Please review
      the referenced CVE identifiers for details.
    </p>
    
  </description>
  <impact type="normal">
    <p>A remote attacker could possibly execute arbitrary code with the
      privileges of the process, cause a Denial of Service condition, or have
      other unspecified impacts.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All PCRE2 users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=dev-libs/libpcre2-10.30"
    </code>
    
    <p>Packages which depend on this library may need to be recompiled. Tools
      such as revdep-rebuild may assist in identifying some of these packages.
    </p>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7186">
      CVE-2017-7186
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8399">
      CVE-2017-8399
    </uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8786">
      CVE-2017-8786
    </uri>
  </references>
  <metadata tag="requester" timestamp="2017-09-19T01:23:39Z">chrisadr</metadata>
  <metadata tag="submitter" timestamp="2017-10-08T14:42:50Z">chrisadr</metadata>
</glsa>