blob: 438a46004717158a234fd25e530897953cd5f953 (
plain) (
blame)
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
|
Candidate: CVE-2004-0394
References:
CONECTIVA:CLA-2004:846
URL:http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000846
GENTOO:GLSA-200407-02
URL:http://security.gentoo.org/glsa/glsa-200407-02.xml
MANDRAKE:MDKSA-2004:037
URL:http://www.mandrakesoft.com/security/advisories?name=MDKSA-2004:037
MLIST:[fedora-announce] 20040422 Fedora alert FEDORA-2004-111 (kernel)
URL:http://lwn.net/Articles/81773/
ENGARDE:ESA-20040428-004
URL:http://www.linuxsecurity.com/advisories/engarde_advisory-4285.html
SGI:20040504-01-U
URL:ftp://patches.sgi.com/support/free/security/advisories/20040504-01-U.asc
SGI:20040505-01-U
URL:ftp://patches.sgi.com/support/free/security/advisories/20040505-01-U.asc
SUSE:SuSE-SA:2004:010
URL:http://www.novell.com/linux/security/advisories/2004_10_kernel.html
XF:linux-panic-bo(15953)
URL:http://xforce.iss.net/xforce/xfdb/15953
Description:
A "potential" buffer overflow exists in the panic() function in Linux 2.4.x,
although it may not be exploitable due to the functionality of panic.
Notes:
jmm> I've verified 2.6.8 to contain the correct vsnprintf() call
jmm> For 2.4 it's fixed in 2.4.32, but unfixed in 2.4.27. I'm marking it
jmm> needed, although I guess it's not exploitable
Bugs:
upstream: released (2.4.28-pre1)
linux-2.6: N/A
2.6.8-sarge-security: N/A
2.4.27-sarge-security: released (2.4.27-1)
2.4.19-woody-security: released (2.4.19-4.woody3)
2.4.18-woody-security: released (2.4.18-14.4)
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.18)
2.4.18-woody-security-hppa: released (62.4)
|
