blob: f0c8cfaa53c9590a7145841fe1d37e7dc7f287de (
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
71
72
73
74
75
76
77
78
79
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201412-47">
<title>TORQUE Resource Manager: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been found in TORQUE Resource
Manager, possibly resulting in escalation of privileges or remote code
execution.
</synopsis>
<product type="ebuild">torque</product>
<announced>2014-12-26</announced>
<revised>2014-12-26: 1</revised>
<bug>372959</bug>
<bug>378805</bug>
<bug>390167</bug>
<bug>484320</bug>
<bug>491270</bug>
<bug>510726</bug>
<access>local, remote</access>
<affected>
<package name="sys-cluster/torque" auto="yes" arch="*">
<unaffected range="ge">4.1.7</unaffected>
<unaffected range="rge">2.5.13</unaffected>
<vulnerable range="lt">4.1.7</vulnerable>
</package>
</affected>
<background>
<p>TORQUE is a resource manager and queuing system based on OpenPBS.</p>
</background>
<description>
<p>Multiple vulnerabilities have been discovered in TORQUE Resource
Manager. Please review the CVE identifiers referenced below for details.
</p>
</description>
<impact type="high">
<p>A context-dependent attacker may be able to gain escalated privileges,
execute arbitrary code, or bypass security restrictions.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All TORQUE Resource Manager 4.x users should upgrade to the latest
version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-cluster/torque-4.1.7"
</code>
<p>All TORQUE Resource Manager 2.x users should upgrade to the latest
version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-cluster/torque-2.5.13"
</code>
<p>NOTE: One or more of the issues described in this advisory have been
fixed in previous updates. They are included in this advisory for the
sake of completeness. It is likely that your system is already no longer
affected by them.
</p>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2193">CVE-2011-2193</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2907">CVE-2011-2907</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4925">CVE-2011-4925</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4319">CVE-2013-4319</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4495">CVE-2013-4495</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0749">CVE-2014-0749</uri>
</references>
<metadata tag="requester" timestamp="2011-10-07T23:38:08Z">
underling
</metadata>
<metadata tag="submitter" timestamp="2014-12-26T19:24:57Z">ackle</metadata>
</glsa>
|