From f3581ec9b2d48c6103c22fecb46f713217d834e8 Mon Sep 17 00:00:00 2001 From: dann frazier Date: Thu, 17 Aug 2006 00:24:25 +0000 Subject: 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 --- retired/CVE-2003-0462 | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 retired/CVE-2003-0462 (limited to 'retired/CVE-2003-0462') diff --git a/retired/CVE-2003-0462 b/retired/CVE-2003-0462 new file mode 100644 index 000000000..b5d9c8b42 --- /dev/null +++ b/retired/CVE-2003-0462 @@ -0,0 +1,47 @@ +Candidate: CVE-2003-0462 +References: + REDHAT:RHSA-2003:198 + URL:http://www.redhat.com/support/errata/RHSA-2003-198.html + REDHAT:RHSA-2003:238 + URL:http://www.redhat.com/support/errata/RHSA-2003-238.html + DEBIAN:DSA-358 + URL:http://www.debian.org/security/2004/dsa-358 + DEBIAN:DSA-423 + URL:http://www.debian.org/security/2004/dsa-423 + OVAL:OVAL309 + URL:http://oval.mitre.org/oval/definitions/data/oval309.html +Description: + A race condition in the way env_start and env_end pointers are + initialized in the execve system call and used in fs/proc/base.c + on Linux 2.4 allows local users to cause a denial of service + (crash). +Notes: + The fix for 2.4 went into a larger patch: + http://linux.bkbits.net:8080/linux-2.4/cset@41c68e9bogrpceA9rUJa-xHwBd-P6g?nav=index.html|src/|src/fs|src/fs/proc|related/fs/proc/base.c + However, the patch for 2.6 is much simpler: + http://linux.bkbits.net:8080/linux-2.6/cset@3ff1101fZfOZMtqtcvKc_s-agJpLrQ?nav=index.html|src/|src/fs|src/fs/proc|related/fs/proc/base.c + Unfortunately, it doesn't apply cleanly to 2.4. It looks like + the fix included in 2.4.18-10 just re-typed len in + proc_pid_environ; while in 2.6 len was also retyped in + proc_pid_cmdline. Only the former deals with evn_end/env_start + pointers and the latter doesn't apply cleanly to 2.4, so I'm + just making the proc_pid_environ change. + . + hrm.. maybe there was an earlier patch to 2.4; the above 2.4 + patch didn't go in till 2.4.29, yet it looks like this was + already fixed in our 2.4.27 .orig.tar.gz + . + jmm> I assume this was fixed upstream in 2.4.22-pre10? + jmm> o Fix /proc/self security issue +Bugs: +upstream: released (2.6.1), released (2.4.22-pre10) +linux-2.6: N/A +2.6.8-sarge-security: N/A +2.4.27-sarge-security: N/A +2.4.19-woody-security: released (2.4.19-4.woody3) +2.4.18-woody-security: released (2.4.18-10) +2.4.17-woody-security: released (2.4.17-1woody4) +2.4.16-woody-security: released (2.4.16-1woody3) +2.4.17-woody-security-hppa: released (32.5) +2.4.17-woody-security-ia64: released (011226.14.1) +2.4.18-woody-security-hppa: released (62.4) -- cgit v1.2.3