metadata/glsa/glsa-200710-25.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="200710-25">
  <title>MLDonkey: Privilege escalation</title>
  <synopsis>
    The Gentoo MLDonkey ebuild adds a user to the system with a valid login
    shell and no password.
  </synopsis>
  <product type="ebuild">mldonkey</product>
  <announced>2007-10-24</announced>
  <revised>2007-11-07: 02</revised>
  <bug>189412</bug>
  <access>remote</access>
  <affected>
    <package name="net-p2p/mldonkey" auto="yes" arch="*">
      <unaffected range="ge">2.9.0-r3</unaffected>
      <vulnerable range="lt">2.9.0-r3</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    MLDonkey is a peer-to-peer filesharing client that connects to several
    different peer-to-peer networks, including Overnet and BitTorrent.
    </p>
  </background>
  <description>
    <p>
    The Gentoo MLDonkey ebuild adds a user to the system named "p2p" so
    that the MLDonkey service can run under a user with low privileges.
    With older Portage versions this user is created with a valid login
    shell and no password.
    </p>
  </description>
  <impact type="high">
    <p>
    A remote attacker could log into a vulnerable system as the p2p user.
    This would require an installed login service that permitted empty
    passwords, such as SSH configured with the "PermitEmptyPasswords yes"
    option, a local login console, or a telnet server.
    </p>
  </impact>
  <workaround>
    <p>
    See Resolution.
    </p>
  </workaround>
  <resolution>
    <p>
    Change the p2p user's shell to disallow login. For example, as root run
    the following command:
    </p>
    <code>
    # usermod -s /bin/false p2p</code>
    <p>
    NOTE: updating to the current MLDonkey ebuild will not remove this
    vulnerability, it must be fixed manually. The updated ebuild is to
    prevent this problem from occurring in the future.
    </p>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5714">CVE-2007-5714</uri>
  </references>
  <metadata tag="requester" timestamp="2007-09-10T16:21:11Z">
    jaervosz
  </metadata>
  <metadata tag="submitter" timestamp="2007-10-07T16:40:51Z">
    aetius
  </metadata>
  <metadata tag="bugReady" timestamp="2007-10-07T19:26:05Z">
    p-y
  </metadata>
</glsa>