summaryrefslogtreecommitdiff
blob: 8fd38c398a745db2961b9983f67e26eb6d9a9270 (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
56
57
58
59
60
61
62
63
64
65
66
67
68
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200408-15">
  <title>Tomcat: Insecure installation</title>
  <synopsis>
    Improper file ownership may allow a member of the tomcat group to execute
    scripts as root.
  </synopsis>
  <product type="ebuild">tomcat</product>
  <announced>2004-08-15</announced>
  <revised count="04">2006-05-22</revised>
  <bug>59232</bug>
  <access>local</access>
  <affected>
    <package name="www-servers/tomcat" auto="yes" arch="*">
      <unaffected range="ge">5.0.27-r3</unaffected>
      <unaffected range="rge">4.1.30-r4</unaffected>
      <unaffected range="rge">3.3.2-r2</unaffected>
      <vulnerable range="lt">5.0.27-r3</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    Tomcat is the Apache Jakarta Project's official implementation of Java
    Servlets and Java Server Pages.
    </p>
  </background>
  <description>
    <p>
    The Gentoo ebuild for Tomcat sets the ownership of the Tomcat init
    scripts as tomcat:tomcat, but those scripts are executed with root
    privileges when the system is started. This may allow a member of the
    tomcat group to run arbitrary code with root privileges when the Tomcat
    init scripts are run.
    </p>
  </description>
  <impact type="normal">
    <p>
    This could lead to a local privilege escalation or root compromise by
    authenticated users.
    </p>
  </impact>
  <workaround>
    <p>
    Users may change the ownership of /etc/init.d/tomcat* and
    /etc/conf.d/tomcat* to be root:root:
    </p>
    <code>
    # chown -R root:root /etc/init.d/tomcat*
    # chown -R root:root /etc/conf.d/tomcat*</code>
  </workaround>
  <resolution>
    <p>
    All Tomcat users can upgrade to the latest stable version, or simply
    apply the workaround:
    </p>
    <code>
    # emerge sync
    # emerge -pv "&gt;=www-servers/tomcat-5.0.27-r3"
    # emerge "&gt;=www-servers/tomcat-5.0.27-r3"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1452">CVE-2004-1452</uri>
  </references>
  <metadata tag="submitter" timestamp="2004-08-08T20:54:24Z">
    dmargoli
  </metadata>
</glsa>