glsa-200502-12.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
67
68
69
70
71
72

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200502-12">
  <title>Webmin: Information leak in Gentoo binary package</title>
  <synopsis>
    Portage-built Webmin binary packages accidentally include a file containing
    the local encrypted root password.
  </synopsis>
  <product type="ebuild">Webmin</product>
  <announced>2005-02-11</announced>
  <revised>2006-05-22: 02</revised>
  <bug>77731</bug>
  <access>remote</access>
  <affected>
    <package name="app-admin/webmin" auto="yes" arch="*">
      <unaffected range="ge">1.170-r3</unaffected>
      <vulnerable range="lt">1.170-r3</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    Webmin is a web-based system administration console allowing an
    administrator to easily configure servers and other features. Using the
    'buildpkg' FEATURE, or the -b/-B emerge options, Portage can build
    reusable binary packages for any of the packages available through the
    Portage tree.
    </p>
  </background>
  <description>
    <p>
    Tavis Ormandy of the Gentoo Linux Security Audit Team discovered that
    the Webmin ebuild contains a design flaw. It imports the encrypted
    local root password into the miniserv.users file before building binary
    packages that include this file.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could retrieve Portage-built Webmin binary packages
    and recover the encrypted root password from the build host.
    </p>
  </impact>
  <workaround>
    <p>
    Users who never built or shared a Webmin binary package are unaffected
    by this.
    </p>
  </workaround>
  <resolution>
    <p>
    Webmin users should delete any old shared Webmin binary package as soon
    as possible. They should also consider their buildhost root password
    potentially exposed and follow proper audit procedures.
    </p>
    <p>
    If you plan to build binary packages, you should upgrade to the latest
    version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=app-admin/webmin-1.170-r3"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0427">CVE-2005-0427</uri>
  </references>
  <metadata tag="submitter" timestamp="2005-02-10T15:50:39Z">
    koon
  </metadata>
  <metadata tag="bugReady" timestamp="2005-02-10T15:50:49Z">
    koon
  </metadata>
</glsa>