summaryrefslogtreecommitdiff
blob: a485d7a4e28d7f99a68c62ceb1272c628b50ff88 (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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201604-02">
  <title>Xalan-Java: Arbitrary code execution</title>
  <synopsis>Insufficient constraints in Apache's Xalan-Java might allow remote
    attackers to execute arbitrary code and load arbitrary classes.
  </synopsis>
  <product type="ebuild">xalan-java</product>
  <announced>2016-04-02</announced>
  <revised>2016-04-02: 1</revised>
  <bug>505602</bug>
  <access>remote</access>
  <affected>
    <package name="dev-java/xalan" auto="yes" arch="*">
      <unaffected range="ge">2.7.2</unaffected>
      <vulnerable range="lt">2.7.2</vulnerable>
    </package>
  </affected>
  <background>
    <p>Xalan-Java is an XSLT processor for transforming XML documents into
      HTML, text, or other XML document types.
    </p>
  </background>
  <description>
    <p>The TransformerFactory in Apache Xalan-Java does not properly restrict
      access to certain properties when FEATURE_SECURE_PROCESSING is enabled.
      This can also be exploited via a Java property that is bound to the XSLT
      1.0 system-property function.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could inject specially crafted XSLT properties
      resulting in the execution of arbitrary code with the privileges of the
      process.
    </p>
  </impact>
  <workaround>
    <p>There is no known work around at this time.</p>
  </workaround>
  <resolution>
    <p>All Xalan-Java users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=dev-java/xalan-2.7.2"
    </code>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0107">CVE-2014-0107</uri>
  </references>
  <metadata tag="requester" timestamp="2016-03-04T11:55:40Z">b-man</metadata>
  <metadata tag="submitter" timestamp="2016-04-02T19:42:25Z">b-man</metadata>
</glsa>