OpenBSD ibcs2_exec.c and exec_elf.c denial of service
|openbsd-ibcs2exe-execelf-dos (13614)||Medium Risk|
OpenBSD is vulnerable to a denial of service, caused by a vulnerability in the ibcs2_exec.c and exec_elf.c files. By creating a malformed binary containing an invalid header, a local attacker could cause a kernel panic, once the binary is executed.
Denial of Service
For OpenBSD 2.8:
No remedy available as of November 2003. OpenBSD has not indicated whether a patch will be available for this version.
For OpenBSD 3.3:
Apply the patch for this vulnerability (010: RELIABILITY FIX: November 4, 2003), available from the OpenBSD 3.3 errata Web page. See References.
For OpenBSD 3.4:
Apply the patch for this vulnerability (005: RELIABILITY FIX: November 4, 2003), available from the OpenBSD 3.4 errata Web page. See References.
- Georgi Guninski Security Advisory #63, 2003: OpenBSD kernel panic, yet still *BSD much better than windows.
- OpenBSD 3.3 errata Web page: 010: RELIABILITY FIX: November 4, 2003.
- OpenBSD 3.4 errata Web page: 005: RELIABILITY FIX: November 4, 2003.
- BID-8978: OpenBSD Local Malformed Binary Execution Denial of Service Vulnerability
- CVE-2003-0955: OpenBSD kernel 3.3 and 3.4 allows local users to cause a denial of service (kernel panic) and possibly execute arbitrary code in 3.4 via a program with an invalid header that is not properly handled by (1) ibcs2_exec.c in the iBCS2 emulation (compat_ibcs2) or (2) exec_elf.c, which leads to a stack-based buffer overflow.
- OSVDB ID: 2832: OpenBSD compat_ibcs2 Overflow
- OpenBSD OpenBSD 2.8
- OpenBSD OpenBSD 3.3
Nov 04, 2003
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this