version 1.94, 2019/05/27 22:55:19 |
version 1.95, 2019/05/28 16:32:41 |
|
|
<hr> |
<hr> |
|
|
<ul> |
<ul> |
<li id="uucp"> |
|
<strong>033: SECURITY FIX: September 11, 2001</strong> |
<li id="zsconsole"> |
<i>All architectures</i><br> |
<strong>001: RELIABILITY FIX: Nov 10, 2000</strong><br> |
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/uuxqt.8">uuxqt(8)</a> |
When running a sparc with a serial console, certain types of interrupts would |
that may allow an attacker to run arbitrary commands as user uucp and |
cause great grief.<br> |
use this to gain root access. |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/001_zsconsole.patch"> |
The UUCP execution daemon, uuxqt(8), has a bug in its command line |
|
parsing routine may allow arbitrary commands to be run. Because |
|
some UUCP commands are run as root (and daemon) from cron it is possible |
|
to leverage compromise of the UUCP user to gain root. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/033_uucp.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="lpd"> |
|
<strong>032: SECURITY FIX: August 29, 2001</strong> |
<li id="skey"> |
|
<strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/lpd.8">lpd(8)</a> |
In ssh(1), skey support for SSH1 protocol was broken. Some people might consider |
that may allow an attacker with line printer access to gain root |
that kind of important.<br> |
privileges. A machine must be running lpd to be vulnerable (OpenBSD |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/002_sshskey.patch"> |
does not start lpd by default). Only machines with line printer |
|
access (ie: listed in either /etc/hosts.lpd or /etc/hosts.equiv) |
|
may be used to mount an attack. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/032_lpd.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="sendmail2"> |
|
<strong>031: SECURITY FIX: August 21, 2001</strong> |
<li id="qe"> |
<i>All architectures</i><br> |
<strong>003: RELIABILITY FIX: Nov 17, 2000</strong><br> |
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a> |
Configuring a qec+qe causes a NMI panic.<br> |
that may allow an attacker on the local host to gain root privileges by |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/003_qe.patch"> |
specifying out-of-bounds debug parameters. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/031_sendmail.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="kernexec"> |
|
<strong>030: SECURITY FIX: June 15, 2001</strong> |
<li id="rijndael"> |
|
<strong>004: RELIABILITY FIX: Nov 17, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
A race condition exists in the kernel <a href="https://man.openbsd.org/OpenBSD-2.8/execve.2">execve(2)</a> implementation that opens a small window of vulnerability for a non-privileged user to <a href="https://man.openbsd.org/OpenBSD-2.8/ptrace.2">ptrace(2)</a> attach to a suid/sgid process. |
First off, AES (Rijndael) encryption and decryption were broken for IPsec |
<br> |
and swap encryption.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/030_kernexec.patch"> |
Secondly, the AES code did not work properly on big endian machines.<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/004_rijndael.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
|
This is the second revision of the patch. |
<p> |
<p> |
<li id="fts"> |
|
<strong>029: SECURITY FIX: May 30, 2001</strong> |
<li id="ftpd"> |
|
<strong>005: SECURITY FIX: Dec 4, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Programs using the <a href="https://man.openbsd.org/OpenBSD-2.8/fts.3">fts(3)</a> |
OpenBSD 2.8's ftpd contains a one-byte overflow in the replydirname() function.<br> |
routines (such as rm, find, and most programs that take a <b>-R</b> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/005_ftpd.patch"> |
flag) can be tricked into changing into the wrong directory if the |
|
parent dir is changed out from underneath it. This is similar to |
|
the old fts bug but happens when popping out of directories, as |
|
opposed to descending into them. |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/029_fts.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
This is the second version of the patch. |
You can view the <a href="advisories/ftpd_replydirname.txt">OpenBSD Advisory</a> here. |
<p> |
<p> |
<li id="sendmail"> |
|
<strong>028: SECURITY FIX: May 29, 2001</strong> |
<li id="pcibios"> |
|
<strong>006: STABILITY FIX: Dec 4, 2000</strong><br> |
|
On some machines, a PCIBIOS device driver interrupt allocation bug can cause a |
|
kernel hang while probing PCI devices. If you have this symptom, you can disable |
|
PCIBIOS as a workaround. To do this, |
|
<ul> |
|
<li>Enter the User Kernel Configuration by booting with the |
|
option "boot -c". |
|
<li>Once at the <i>UKC></i> prompt, enter |
|
<blockquote><pre> |
|
UKC> disable pcibios |
|
UKC> quit<!-- |
|
--></pre></blockquote> |
|
<li>See <a href="./faq/faq5.html#5.6">this page</a> after a successful |
|
boot for instructions on how to re-write your kernel to disable PCIBIOS |
|
permanently. |
|
</ul> |
|
<p> |
|
|
|
<li id="x_sun3"> |
|
<strong>007: INSTALL PROBLEM: Dec 4, 2000</strong><br> |
|
The X packages |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xshare28.tgz">share28.tgz</a> |
|
and |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xfont28.tgz">font28.tgz</a> |
|
were not on the CD, and only available via FTP install. These packages can be |
|
added post-install by using the following command: |
|
<pre> |
|
# cd /; tar xvfpz xshare28.tgz |
|
# cd /; tar xvfpz xfont28.tgz |
|
</pre> |
|
<p> |
|
|
|
<li id="kerberos"> |
|
<strong>008: SECURITY FIX: Dec 7, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
The signal handlers in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a> contain code that is unsafe in the |
Two problems have recently been discovered in the KerberosIV code.<p> |
context of a signal handler. This leads to potentially serious |
1. A symlink problem was discovered in the KerberosIV password checking |
race conditions. At the moment this is a theoretical attack only |
routines /usr/bin/su and /usr/bin/login, which makes it possible for a |
and can only be exploited on the local host (if at all).<br> |
local user to overwrite any file on the local machine.<p> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/028_sendmail.patch"> |
2. It is possible to specify environment variables in telnet |
|
which will be passed over the to the remote host. This makes it |
|
possible to set environment variables on the remote side, including |
|
ones that have special meaning on the server. It is not clear at this |
|
time what the impact is, but we recommend everyone to upgrade their |
|
machines immediately.<p> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/008_kerberos.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
It updates sendmail to version 8.11.4. |
|
<p> |
<p> |
<li id="ipf_frag"> |
|
<strong>027: SECURITY FIX: Apr 23, 2001</strong> |
<li id="kerberos2"> |
|
<strong>009: SECURITY FIX: Dec 10, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
IPF has a serious problem with fragment caching, the bug is triggered if you use the ipf(5) syntax "keep state".<br> |
Another problem exists in the Kerberos libraries.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/027_ipf-frag.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/009_kerberos2.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="glob_limit"> |
|
<strong>026: SECURITY FIX: Apr 23, 2001</strong> |
<li id="fastroute"> |
|
<strong>010: RELIABILITY FIX: Dec 11, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">ftpd(8)</a> has a potential DoS related to <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a>. This patch introduces a GLOB_LIMIT, eliminating the DoS. You must have <a href="#glob">025_glob.patch</a> installed before installing this patch.<br> |
A crash could occur during fast routing, if IPSEC was enabled.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/026_globlimit.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/010_fastroute.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="glob"> |
|
<strong>025: SECURITY FIX: Apr 10, 2001</strong> |
<li id="hwcrypto"> |
|
<strong>011: RELIABILITY FIX: Dec 13, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a> contains multiple buffer overflows. <br> |
The crypto subsystem could incorrectly fail to run certain software ciphers, |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/025_glob.patch"> |
if a hardware card existed in the machine.<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/011_hwcrypto.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="readline"> |
|
<strong>024: SECURITY FIX: Mar 18, 2001</strong> |
<li id="imacdv"> |
<i>All architectures</i><br> |
<strong>012: INSTALL PROBLEM: Dec 14, 2000</strong><br> |
The readline library shipped with OpenBSD allows history files creation |
The IMac DV+ (and probably some other machines) incorrectly identify their video |
with a permissive |
hardware, but it is possible to work around the problem.<br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/umask.2">umask(2)</a>. |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/012_imacdv.patch"> |
This can lead to the leakage of sensitive information in applications |
|
that use passwords and the like during user interaction (one such |
|
application is mysql).<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/024_readline.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="ipsec_ah"> |
|
<strong>023: SECURITY FIX: Mar 2, 2001</strong> |
<li id="procfs"> |
|
<strong>013: SECURITY FIX: Dec 18, 2000</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Insufficient checks in the IPSEC AH IPv4 option handling code can lead to a buffer overrun leading to a remote DoS. This option is not on by default.<br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/mount_procfs.8">Procfs</a> contained numerous overflows, which could lead an intruder to root permissions. Procfs is NOT enabled by default in OpenBSD. <br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/023_ip_ah.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/013_procfs.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="userldt"> |
|
<strong>022: SECURITY FIX: Mar 2, 2001</strong><br> |
<li id="xlock"> |
The <b>USER_LDT</b> kernel option allows an attacker to gain access to privileged areas of kernel memory. This option is not on by default. |
<strong>014: SECURITY FIX: Dec 22, 2000</strong> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/022_userltd.patch"> |
<i>All architectures</i><br> |
|
Improve xlock(1)'s authentication by authenticating via a pipe in an early forked process. No known vulnerability exists, this is just a precautionary patch.<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/014_xlock.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="sudo"> |
In addition to a source code patch, new xlock binaries have been created for each architecture listed below. Place these binaries at <i>/usr/X11R6/bin/xlock</i> |
<strong>021: SECURITY FIX: Feb 22, 2001</strong> |
and <i>chmod 4755 /usr/X11R6/bin/xlock</i>. |
<i>All architectures</i><br> |
<p> |
There is an exploitable heap corruption bug in |
<ul> |
<a href="https://man.openbsd.org/OpenBSD-2.8/sudo.8">sudo</a>. |
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/xlock">Xlock - i386</a> |
<br> |
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/xlock">Xlock - sparc</a> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/021_sudo.patch"> |
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mac68k/xlock">Xlock - mac68k</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/xlock">Xlock - powerpc</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/amiga/xlock">Xlock - amiga</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/hp300/xlock">Xlock - hp300</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mvme68k/xlock">Xlock - mvme68k</a> |
|
</ul> |
|
<p> |
|
|
|
<li id="pms"> |
|
<strong>015: STABILITY FIX: Dec 22, 2000</strong><br> |
|
Some machines locked up while trying to use the mouse in console mode. This patch solves that problem.<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/015_pms.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="libwrap"> |
|
<strong>020: IMPLEMENTATION FIX: Feb 15, 2001</strong> |
<li id="tl"> |
|
<strong>016: RELIABILITY FIX: Jan 4, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Client side ident protocol was broken in libwrap, affecting anything using libwrap including <a href="https://man.openbsd.org/OpenBSD-2.8/tcpd.8">tcpd</a>. The effect of this was that libwrap would never retrieve and log ident values from remote hosts on connections.<br> |
Allow ThunderLAN cards to share interrupts nicely.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/020_libwrap.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/016_tl.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="lepci"> |
|
<strong>019: IMPLEMENTATION FIX: Jan 31, 2001</strong> |
<li id="rnd"> |
|
<strong>017: SECURITY FIX: Jan 22, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Fix memory allocation in the PCI LANCE driver, <a href="https://man.openbsd.org/OpenBSD-2.8/le.4">le</a>. A side effect of this is that OpenBSD under VMWare now works again.<br> |
The <a href="https://man.openbsd.org/OpenBSD-2.8/random.4">rnd(4)</a> device does not use all of its input when data is written to it.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/019_lepci.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/017_rnd.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
|
|
<li id="named"> |
<li id="named"> |
<strong>018: SECURITY FIX: Jan 29, 2001</strong> |
<strong>018: SECURITY FIX: Jan 29, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
|
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/018_named.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/018_named.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="rnd"> |
|
<strong>017: SECURITY FIX: Jan 22, 2001</strong> |
<li id="lepci"> |
|
<strong>019: IMPLEMENTATION FIX: Jan 31, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
The <a href="https://man.openbsd.org/OpenBSD-2.8/random.4">rnd(4)</a> device does not use all of its input when data is written to it.<br> |
Fix memory allocation in the PCI LANCE driver, <a href="https://man.openbsd.org/OpenBSD-2.8/le.4">le</a>. A side effect of this is that OpenBSD under VMWare now works again.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/017_rnd.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/019_lepci.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="tl"> |
|
<strong>016: RELIABILITY FIX: Jan 4, 2001</strong> |
<li id="libwrap"> |
|
<strong>020: IMPLEMENTATION FIX: Feb 15, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Allow ThunderLAN cards to share interrupts nicely.<br> |
Client side ident protocol was broken in libwrap, affecting anything using libwrap including <a href="https://man.openbsd.org/OpenBSD-2.8/tcpd.8">tcpd</a>. The effect of this was that libwrap would never retrieve and log ident values from remote hosts on connections.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/016_tl.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/020_libwrap.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="pms"> |
|
<strong>015: STABILITY FIX: Dec 22, 2000</strong><br> |
<li id="sudo"> |
Some machines locked up while trying to use the mouse in console mode. This patch solves that problem.<br> |
<strong>021: SECURITY FIX: Feb 22, 2001</strong> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/015_pms.patch"> |
<i>All architectures</i><br> |
|
There is an exploitable heap corruption bug in |
|
<a href="https://man.openbsd.org/OpenBSD-2.8/sudo.8">sudo</a>. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/021_sudo.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="xlock"> |
|
<strong>014: SECURITY FIX: Dec 22, 2000</strong> |
<li id="userldt"> |
<i>All architectures</i><br> |
<strong>022: SECURITY FIX: Mar 2, 2001</strong><br> |
Improve xlock(1)'s authentication by authenticating via a pipe in an early forked process. No known vulnerability exists, this is just a precautionary patch.<br> |
The <b>USER_LDT</b> kernel option allows an attacker to gain access to privileged areas of kernel memory. This option is not on by default. |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/014_xlock.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/022_userltd.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
In addition to a source code patch, new xlock binaries have been created for each architecture listed below. Place these binaries at <i>/usr/X11R6/bin/xlock</i> |
|
and <i>chmod 4755 /usr/X11R6/bin/xlock</i>. |
<li id="ipsec_ah"> |
<p> |
<strong>023: SECURITY FIX: Mar 2, 2001</strong> |
<ul> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/xlock">Xlock - i386</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/xlock">Xlock - sparc</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mac68k/xlock">Xlock - mac68k</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/xlock">Xlock - powerpc</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/amiga/xlock">Xlock - amiga</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/hp300/xlock">Xlock - hp300</a> |
|
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mvme68k/xlock">Xlock - mvme68k</a> |
|
</ul> |
|
<p> |
|
<li id="procfs"> |
|
<strong>013: SECURITY FIX: Dec 18, 2000</strong> |
|
<i>All architectures</i><br> |
<i>All architectures</i><br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/mount_procfs.8">Procfs</a> contained numerous overflows, which could lead an intruder to root permissions. Procfs is NOT enabled by default in OpenBSD. <br> |
Insufficient checks in the IPSEC AH IPv4 option handling code can lead to a buffer overrun leading to a remote DoS. This option is not on by default.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/013_procfs.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/023_ip_ah.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="imacdv"> |
|
<strong>012: INSTALL PROBLEM: Dec 14, 2000</strong><br> |
<li id="readline"> |
The IMac DV+ (and probably some other machines) incorrectly identify their video |
<strong>024: SECURITY FIX: Mar 18, 2001</strong> |
hardware, but it is possible to work around the problem.<br> |
<i>All architectures</i><br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/012_imacdv.patch"> |
The readline library shipped with OpenBSD allows history files creation |
|
with a permissive |
|
<a href="https://man.openbsd.org/OpenBSD-2.8/umask.2">umask(2)</a>. |
|
This can lead to the leakage of sensitive information in applications |
|
that use passwords and the like during user interaction (one such |
|
application is mysql).<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/024_readline.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="hwcrypto"> |
|
<strong>011: RELIABILITY FIX: Dec 13, 2000</strong> |
<li id="glob"> |
|
<strong>025: SECURITY FIX: Apr 10, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
The crypto subsystem could incorrectly fail to run certain software ciphers, |
<a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a> contains multiple buffer overflows. <br> |
if a hardware card existed in the machine.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/025_glob.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/011_hwcrypto.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="fastroute"> |
|
<strong>010: RELIABILITY FIX: Dec 11, 2000</strong> |
<li id="glob_limit"> |
|
<strong>026: SECURITY FIX: Apr 23, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
A crash could occur during fast routing, if IPSEC was enabled.<br> |
<a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">ftpd(8)</a> has a potential DoS related to <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a>. This patch introduces a GLOB_LIMIT, eliminating the DoS. You must have <a href="#glob">025_glob.patch</a> installed before installing this patch.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/010_fastroute.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/026_globlimit.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="kerberos2"> |
|
<strong>009: SECURITY FIX: Dec 10, 2000</strong> |
<li id="ipf_frag"> |
|
<strong>027: SECURITY FIX: Apr 23, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Another problem exists in the Kerberos libraries.<br> |
IPF has a serious problem with fragment caching, the bug is triggered if you use the ipf(5) syntax "keep state".<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/009_kerberos2.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/027_ipf-frag.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="kerberos"> |
|
<strong>008: SECURITY FIX: Dec 7, 2000</strong> |
<li id="sendmail"> |
|
<strong>028: SECURITY FIX: May 29, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
Two problems have recently been discovered in the KerberosIV code.<p> |
The signal handlers in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a> contain code that is unsafe in the |
1. A symlink problem was discovered in the KerberosIV password checking |
context of a signal handler. This leads to potentially serious |
routines /usr/bin/su and /usr/bin/login, which makes it possible for a |
race conditions. At the moment this is a theoretical attack only |
local user to overwrite any file on the local machine.<p> |
and can only be exploited on the local host (if at all).<br> |
2. It is possible to specify environment variables in telnet |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/028_sendmail.patch"> |
which will be passed over the to the remote host. This makes it |
|
possible to set environment variables on the remote side, including |
|
ones that have special meaning on the server. It is not clear at this |
|
time what the impact is, but we recommend everyone to upgrade their |
|
machines immediately.<p> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/008_kerberos.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
|
It updates sendmail to version 8.11.4. |
<p> |
<p> |
<li id="x_sun3"> |
|
<strong>007: INSTALL PROBLEM: Dec 4, 2000</strong><br> |
<li id="fts"> |
The X packages |
<strong>029: SECURITY FIX: May 30, 2001</strong> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xshare28.tgz">share28.tgz</a> |
|
and |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xfont28.tgz">font28.tgz</a> |
|
were not on the CD, and only available via FTP install. These packages can be |
|
added post-install by using the following command: |
|
<pre> |
|
# cd /; tar xvfpz xshare28.tgz |
|
# cd /; tar xvfpz xfont28.tgz |
|
</pre> |
|
<p> |
|
<li id="pcibios"> |
|
<strong>006: STABILITY FIX: Dec 4, 2000</strong><br> |
|
On some machines, a PCIBIOS device driver interrupt allocation bug can cause a |
|
kernel hang while probing PCI devices. If you have this symptom, you can disable |
|
PCIBIOS as a workaround. To do this, |
|
<ul> |
|
<li>Enter the User Kernel Configuration by booting with the |
|
option "boot -c". |
|
<li>Once at the <i>UKC></i> prompt, enter |
|
<blockquote><pre> |
|
UKC> disable pcibios |
|
UKC> quit<!-- |
|
--></pre></blockquote> |
|
<li>See <a href="./faq/faq5.html#5.6">this page</a> after a successful |
|
boot for instructions on how to re-write your kernel to disable PCIBIOS |
|
permanently. |
|
</ul> |
|
<p> |
|
<li id="ftpd"> |
|
<strong>005: SECURITY FIX: Dec 4, 2000</strong> |
|
<i>All architectures</i><br> |
<i>All architectures</i><br> |
OpenBSD 2.8's ftpd contains a one-byte overflow in the replydirname() function.<br> |
Programs using the <a href="https://man.openbsd.org/OpenBSD-2.8/fts.3">fts(3)</a> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/005_ftpd.patch"> |
routines (such as rm, find, and most programs that take a <b>-R</b> |
|
flag) can be tricked into changing into the wrong directory if the |
|
parent dir is changed out from underneath it. This is similar to |
|
the old fts bug but happens when popping out of directories, as |
|
opposed to descending into them. |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/029_fts.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
You can view the <a href="advisories/ftpd_replydirname.txt">OpenBSD Advisory</a> here. |
This is the second version of the patch. |
<p> |
<p> |
<li id="rijndael"> |
|
<strong>004: RELIABILITY FIX: Nov 17, 2000</strong> |
<li id="kernexec"> |
|
<strong>030: SECURITY FIX: June 15, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
First off, AES (Rijndael) encryption and decryption were broken for IPsec |
A race condition exists in the kernel <a href="https://man.openbsd.org/OpenBSD-2.8/execve.2">execve(2)</a> implementation that opens a small window of vulnerability for a non-privileged user to <a href="https://man.openbsd.org/OpenBSD-2.8/ptrace.2">ptrace(2)</a> attach to a suid/sgid process. |
and swap encryption.<br> |
<br> |
Secondly, the AES code did not work properly on big endian machines.<br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/030_kernexec.patch"> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/004_rijndael.patch"> |
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
This is the second revision of the patch. |
|
<p> |
<p> |
<li id="qe"> |
|
<strong>003: RELIABILITY FIX: Nov 17, 2000</strong><br> |
<li id="sendmail2"> |
Configuring a qec+qe causes a NMI panic.<br> |
<strong>031: SECURITY FIX: August 21, 2001</strong> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/003_qe.patch"> |
<i>All architectures</i><br> |
|
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a> |
|
that may allow an attacker on the local host to gain root privileges by |
|
specifying out-of-bounds debug parameters. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/031_sendmail.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="skey"> |
|
<strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong> |
<li id="lpd"> |
|
<strong>032: SECURITY FIX: August 29, 2001</strong> |
<i>All architectures</i><br> |
<i>All architectures</i><br> |
In ssh(1), skey support for SSH1 protocol was broken. Some people might consider |
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/lpd.8">lpd(8)</a> |
that kind of important.<br> |
that may allow an attacker with line printer access to gain root |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/002_sshskey.patch"> |
privileges. A machine must be running lpd to be vulnerable (OpenBSD |
|
does not start lpd by default). Only machines with line printer |
|
access (ie: listed in either /etc/hosts.lpd or /etc/hosts.equiv) |
|
may be used to mount an attack. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/032_lpd.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
<li id="zsconsole"> |
|
<strong>001: RELIABILITY FIX: Nov 10, 2000</strong><br> |
<li id="uucp"> |
When running a sparc with a serial console, certain types of interrupts would |
<strong>033: SECURITY FIX: September 11, 2001</strong> |
cause great grief.<br> |
<i>All architectures</i><br> |
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/001_zsconsole.patch"> |
A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/uuxqt.8">uuxqt(8)</a> |
|
that may allow an attacker to run arbitrary commands as user uucp and |
|
use this to gain root access. |
|
The UUCP execution daemon, uuxqt(8), has a bug in its command line |
|
parsing routine may allow arbitrary commands to be run. Because |
|
some UUCP commands are run as root (and daemon) from cron it is possible |
|
to leverage compromise of the UUCP user to gain root. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/033_uucp.patch"> |
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
|
|