← Back to branch summary

~ubuntu-security/ubuntu-cve-tracker/master

« back to all changes in this revision

Viewing changes to retired/CVE-2012-6030

  • Committer: Steve Beattie
  • Date: 2019-02-19 06:18:27 UTC
  • Revision ID: sbeattie@ubuntu.com-20190219061827-oh57fzcfc1u9dlfk
The ubuntu-cve-tracker project has been converted to git.

Please use 'git clone https://git.launchpad.net/ubuntu-cve-tracker' to
get the converted tree.

Show diffs side-by-side

added added

removed removed

Lines of Context:
retired/CVE-2012-6030
1
 
Candidate: CVE-2012-6030
2
 
PublicDate: 2012-11-23
3
 
References:
4
 
 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6030
5
 
 http://xforce.iss.net/xforce/xfdb/78268
6
 
 http://www.securitytracker.com/id?1027482
7
 
 http://www.openwall.com/lists/oss-security/2012/09/05/8
8
 
 http://wiki.xen.org/wiki/Security_Announcements#XSA-15_multiple_TMEM_hypercall_vulnerabilities
9
 
 http://secunia.com/advisories/50472
10
 
 http://osvdb.org/85199
11
 
 http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html
12
 
Description:
13
 
 The do_tmem_op function in the Transcendent Memory (TMEM) in Xen 4.0, 4.1,
14
 
 and 4.2 allow local guest OS users to cause a denial of service (host
15
 
 crash) and possibly have other unspecified impacts via unspecified vectors
16
 
 related to "broken locking checks" in an "error path." NOTE: this issue was
17
 
 originally published as part of CVE-2012-3497, which was too general;
18
 
 CVE-2012-3497 has been SPLIT into this ID and others.
19
 
Ubuntu-Description:
20
 
Notes:
21
 
 sarnold> Xen team strongly recommends against TMEM use
22
 
 mdeslaur> only 4.0 and higher
23
 
 mdeslaur> ONLY installations where "tmem" is specified on the hypervisor command
24
 
 mdeslaur> line are vulnerable.  Most Xen installations do not do so.
25
 
 mdeslaur> upstream says: "TMEM has been described by its maintainers as a
26
 
 mdeslaur> technology preview, and is therefore not supported by them for
27
 
 mdeslaur> use in production systems. Pending a full security audit of the
28
 
 mdeslaur> code, the Xen.org security team recommends that Xen users do not
29
 
 mdeslaur> enable TMEM."
30
 
 mdeslaur> We will not be fixing this in Ubuntu. Marking as "ignored"
31
 
Bugs:
32
 
Priority: low
33
 
Discovered-by:
34
 
Assigned-to:
35
 
 
36
 
Patches_xen-3.1:
37
 
Tags_xen-3.1: universe-binary
38
 
upstream_xen-3.1: needs-triage
39
 
hardy_xen-3.1: not-affected
40
 
lucid_xen-3.1: DNE
41
 
natty_xen-3.1: DNE
42
 
oneiric_xen-3.1: DNE
43
 
precise_xen-3.1: DNE
44
 
quantal_xen-3.1: DNE
45
 
devel_xen-3.1: DNE
46
 
 
47
 
Patches_xen-3.2:
48
 
Tags_xen-3.2: universe-binary
49
 
upstream_xen-3.2: needs-triage
50
 
hardy_xen-3.2: not-affected
51
 
lucid_xen-3.2: DNE
52
 
natty_xen-3.2: DNE
53
 
oneiric_xen-3.2: DNE
54
 
precise_xen-3.2: DNE
55
 
quantal_xen-3.2: DNE
56
 
devel_xen-3.2: DNE
57
 
 
58
 
Patches_xen-3.3:
59
 
Tags_xen-3.3: universe-binary
60
 
upstream_xen-3.3: needs-triage
61
 
hardy_xen-3.3: DNE
62
 
lucid_xen-3.3: not-affected
63
 
natty_xen-3.3: ignored (reached end-of-life)
64
 
oneiric_xen-3.3: DNE
65
 
precise_xen-3.3: DNE
66
 
quantal_xen-3.3: DNE
67
 
devel_xen-3.3: DNE
68
 
 
69
 
Patches_xen:
70
 
Tags_xen: universe-binary
71
 
upstream_xen: needs-triage
72
 
hardy_xen: DNE
73
 
lucid_xen: DNE
74
 
natty_xen: DNE
75
 
oneiric_xen: ignored
76
 
precise_xen: ignored
77
 
quantal_xen: ignored
78
 
devel_xen: ignored
79