summaryrefslogtreecommitdiff
blob: fa0d13a483dad75a4beabe414a157f7e87f27323 (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
69
70
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">

<glsa id="200512-17">
  <title>scponly: Multiple privilege escalation issues</title>
  <synopsis>
    Local users can exploit an scponly flaw to gain root privileges, and
    scponly restricted users can use another vulnerability to evade shell
    restrictions.
  </synopsis>
  <product type="ebuild">scponly</product>
  <announced>December 29, 2005</announced>
  <revised>May 22, 2006: 02</revised>
  <bug>116526</bug>
  <access>local and remote</access>
  <affected>
    <package name="net-misc/scponly" auto="yes" arch="*">
      <unaffected range="ge">4.2</unaffected>
      <vulnerable range="lt">4.2</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    scponly is a restricted shell, allowing only a few predefined commands.
    It is often used as a complement to OpenSSH to provide access to remote
    users without providing any remote execution privileges.
    </p>
  </background>
  <description>
    <p>
    Max Vozeler discovered that the scponlyc command allows users to chroot
    into arbitrary directories. Furthermore, Pekka Pessi reported that
    scponly insufficiently validates command-line parameters to a scp or
    rsync command.
    </p>
  </description>
  <impact type="high">
    <p>
    A local attacker could gain root privileges by chrooting into arbitrary
    directories containing hardlinks to setuid programs. A remote scponly
    user could also send malicious parameters to a scp or rsync command
    that would allow to escape the shell restrictions and execute arbitrary
    programs.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All scponly users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose &quot;&gt;=net-misc/scponly-4.2&quot;</code>
  </resolution>
  <references>
    <uri link="http://sublimation.org/scponly/index.html#relnotes">scponly release notes</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-4532">CVE-2005-4532</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-4533">CVE-2005-4533</uri>
  </references>
  <metadata tag="submitter" timestamp="Tue, 27 Dec 2005 09:38:39 +0000">
    koon
  </metadata>
  <metadata tag="bugReady" timestamp="Thu, 29 Dec 2005 10:10:38 +0000">
    koon
  </metadata>
</glsa>