metadata/glsa/glsa-201311-04.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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201311-04">
  <title>Vixie cron: Denial of service</title>
  <synopsis>A vulnerability has been found in Vixie cron, allowing local
    attackers to conduct symlink attacks. 
  </synopsis>
  <product type="ebuild">vixie-cron</product>
  <announced>2013-11-07</announced>
  <revised count="1">2013-11-07</revised>
  <bug>308055</bug>
  <access>local</access>
  <affected>
    <package name="sys-process/vixie-cron" auto="yes" arch="*">
      <unaffected range="ge">4.1-r14</unaffected>
      <vulnerable range="lt">4.1-r14</vulnerable>
    </package>
  </affected>
  <background>
    <p>Paul Vixie’s cron daemon, a fully featured crond implementation.</p>
  </background>
  <description>
    <p>Vixie cron contains a race condition relating to atime and mtime values
      of temporary files.
    </p>
  </description>
  <impact type="normal">
    <p>A local attacker could change the modification time of files, possibly
      resulting in a Denial of Service condition via a symlink attack.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All Vixie cron users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=sys-process/vixie-cron-4.1-r14"
    </code>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-0424">CVE-2010-0424</uri>
  </references>
  <metadata tag="requester" timestamp="2013-11-04T03:18:24Z">
    BlueKnight
  </metadata>
  <metadata tag="submitter" timestamp="2013-11-07T01:56:36Z">
    BlueKnight
  </metadata>
</glsa>