move retired to the top level hierarchy so people can easily checkout just the active issues

git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@548 e094ebfe-e918-0410-adfb-c712417f3574

1 files changed, 36 insertions, 0 deletions

diff --git a/retired/CVE-2004-0812 b/retired/CVE-2004-0812
new file mode 100644
index 00000000..f6fba4ae
--- /dev/null
+++ b/retired/CVE-2004-0812
@@ -0,0 +1,36 @@
+Candidate: CVE-2004-0812
+References: 
+ REDHAT:RHSA-2004:549
+ URL:http://www.redhat.com/support/errata/RHSA-2004-549.html
+ CONFIRM:http://linux.bkbits.net:8080/linux-2.6/cset@3fad673ber4GuU7iWppydzNIyLntEQ
+ CIAC:P-047
+ URL:http://www.ciac.org/ciac/bulletins/p-047.shtml
+ BID:11794
+ URL:http://www.securityfocus.com/bid/11794
+ SECUNIA:13359
+ URL:http://secunia.com/advisories/13359
+ XF:linux-tss-gain-privilege(18346)
+ URL:http://xforce.iss.net/xforce/xfdb/18346
+Description: 
+ Unknown vulnerability in the Linux kernel before 2.4.23, on the AMD AMD64 and
+ Intel EM64T architectures, associated with "setting up TSS limits," allows
+ local users to cause a denial of service (crash) and possibly execute
+ arbitrary code.
+Notes: 
+ jmm> I've verified that above bkbits fixed is included in 2.6.8, so I'm
+ jmm> marking 2.6 N/A
+ jmm> The vulnerable code doesn't seem to be present in 2.4.27. Plus, 2.4
+ jmm> is unsupported for amd64 anyway, so I'm marking it N/A as well for
+ jmm> the 2.4 kernels
+Bugs: 
+upstream: released (2.6.0-test10)
+linux-2.6: N/A
+2.6.8-sarge-security: N/A
+2.4.27-sarge-security: N/A
+2.4.19-woody-security: N/A
+2.4.18-woody-security: N/A
+2.4.17-woody-security: N/A
+2.4.16-woody-security: N/A
+2.4.17-woody-security-hppa: N/A
+2.4.17-woody-security-ia64: N/A
+2.4.18-woody-security-hppa: N/A