[BACK]Return to errata23.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/errata23.html, Revision 1.22

1.1       deraadt     1: <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
                      2: <html>
                      3: <head>
1.12      deraadt     4: <title>OpenBSD 2.3 errata</title>
1.1       deraadt     5: <link rev=made href=mailto:www@openbsd.org>
                      6: <meta name="resource-type" content="document">
                      7: <meta name="description" content="the OpenBSD CD errata page">
                      8: <meta name="keywords" content="openbsd,cd,errata">
                      9: <meta name="distribution" content="global">
1.18      jufi       10: <meta name="copyright" content="This document copyright 1997-2001 by OpenBSD.">
1.1       deraadt    11: </head>
                     12:
                     13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
                     14:
                     15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
                     16: <h2><font color=#0000e0>
1.4       espie      17: This is the OpenBSD 2.3 release errata &amp; patch list:
1.1       deraadt    18:
                     19: </font></h2>
                     20:
                     21: <hr>
1.13      jason      22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.1       deraadt    23: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
                     24: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
1.8       deraadt    25: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
1.11      deraadt    26: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
1.12      deraadt    27: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
1.15      deraadt    28: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
1.16      deraadt    29: <a href=errata28.html>For 2.8 errata, please refer here</a>.<br>
1.19      deraadt    30: <a href=errata29.html>For 2.9 errata, please refer here</a>.<br>
1.21      deraadt    31: <a href=errata30.html>For 3.0 errata, please refer here</a>.<br>
1.22    ! jufi       32: <a href=errata.html>For 3.1 errata, please refer here</a>.<br>
1.1       deraadt    33: <hr>
                     34:
                     35: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3.tar.gz>
                     36: You can also fetch a tar.gz file containing all the following patches</a>.
                     37: This file is updated once a day.
                     38:
1.14      ericj      39: <p>
                     40: For more detailed information on install patches to OpenBSD, please
                     41: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
                     42:
1.1       deraadt    43: <hr>
                     44:
1.10      deraadt    45: <dl>
1.1       deraadt    46: <a name=all></a>
                     47: <li><h3><font color=#e00000>All architectures</font></h3>
                     48: <ul>
1.5       deraadt    49: <a name=bootpd></a>
                     50: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                     51: A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
                     52: by default, but some people may actually be using it.
1.6       deraadt    53: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/bootpd.patch>
1.7       millert    54: A source code patch exists which remedies this problem</a>, this is the
                     55: second version of the patch.
1.5       deraadt    56: <p>
1.2       deraadt    57: <a name=tcpfix></a>
                     58: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                     59: A remote machine lockup problem exists in the TCP decoding code.
1.6       deraadt    60: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch>
1.2       deraadt    61: A source code patch exists which remedies this problem.</a>
                     62: <p>
1.1       deraadt    63: <a name=atapi></a>
                     64: <li><font color=#009000><strong>HARDWARE SUPPORT</strong></font><br>
                     65: Some ATAPI cdroms which do not support the full mandatory command set,
                     66: (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.
                     67: A patch is
                     68: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch>
                     69: available here.</a>
                     70: <p>
                     71: <a name=chpass></a>
                     72: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                     73: Chpass(1) has a file descriptor leak which allows an
                     74: attacker to modify /etc/master.passwd.
                     75: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch>
                     76: A source code patch exists which remedies this problem.</a>
                     77: <p>
                     78: <a name=resid></a>
                     79: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
                     80: Calling readv(2) with iov_len < 0 or > INT_MAX would result in a
                     81: kernel panic.  This is the third revision of this patch.
                     82: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch>
                     83: A source code patch exists which remedies this problem.</a>
                     84: <p>
                     85: <a name=inetd></a>
                     86: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                     87: Inetd had a file descriptor leak.  A patch is
                     88: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch>
                     89: available here.</a>
                     90: <p>
                     91: <a name=unionfs></a>
                     92: <li><font color=#009000><strong>BUG FIX</strong></font><br>
                     93: As shipped, unionfs had some serious problems.
                     94: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch>
                     95: A patch is available to solve this</a>.
                     96: <p>
                     97: <a name=fdalloc></a>
                     98: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                     99: Some non-allocated file descriptors have implied uses according to
                    100: system libraries, and hence setuid and setgid processes should not
                    101: be executed with these descriptors unallocated.  A patch which forces
                    102: setuid and setgid processes to have some descriptors in fd slots
                    103: 0, 1, and 2 is
                    104: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch>
                    105: available here.</a>
                    106: <p>
1.20      mpech     107: <a name=resolver></a>
1.1       deraadt   108: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.3       deraadt   109: A benign looking buffer overflow in the resolver routines was re-introduced
                    110: accidentally.  The previously fixed behaviour is more correct.  A patch
                    111: to fix this is
                    112: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch>
                    113: available here.</a>
                    114: <p>
                    115: <a name=xlib></a>
                    116: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   117: Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
                    118: libraries. These affect xterm and all other setuid-root programs that
                    119: use these libraries. The problems are associated with buffer overflows
                    120: in code that processes user-supplied data. The Xt library problems
                    121: include those fixed in TOG's recent public patch 3 for X11R6.3. All
                    122: releases of XFree86 up to and including 3.3.2 patch 1 and the version
                    123: distributed with OpenBSD are vulnerable to some or all of these
                    124: problems.
                    125: These problems are fixed in XFree86 patch 2.
                    126: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/XFree86-3.3.2.2.patch>
                    127: The 2nd source patch</a> for these problems, specifically adapted to the
                    128: OpenBSD 2.3 X11 tree, is available now.
                    129: <p>
                    130: <a name=kill></a>
                    131: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                    132: The kill(2) system call previously would permit a large set of signals to
                    133: be delivered to setuid or setgid processes.  If such processes were using
                    134: those signals in dubious ways, this could have resulted in security
                    135: problems of various kinds.
                    136: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch>
                    137: The fourth revision of a source code patch which solves the problem is
                    138: available.</a>
                    139: <p>
                    140: <a name=immutable></a>
                    141: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                    142: A possible new security problem exists if you rely on securelevels and
                    143: immutable or append-only files or character devices.  The fix does not
                    144: permit mmap'ing of immutable or append-only files which are otherwise
1.17      pvalchev  145: writable, as the VM system will bypass the meaning of the file flags
1.1       deraadt   146: when writes happen to the file.
                    147: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch>
                    148: A source code patch exists which remedies this problem.</a>
                    149: <p>
                    150: <a name=ipsec></a>
                    151: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                    152: If IPSEC communication is attempted by starting photurisd(8) (which is
                    153: disabled by default), a system crash may be evoked from remote if
                    154: an attacker uses some classes of invalid packets.
                    155: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>
                    156: A source code patch exists which remedies this problem.</a>
                    157: <p>
                    158: <a name=xterm-xaw></a>
                    159: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                    160: As stated in CERT advisory VB-98.04, there are buffer
                    161: overrun problems in <strong>xterm</strong> related to the input-Method,
                    162: preeditType, and *Keymap resources. Additional buffer overruns exist in
                    163: the <strong>Xaw</strong> library related to the inputMethod and
                    164: preeditType resources.   The xterm(1) problem represents a security
                    165: vulnerability for any platform where xterm is installed setuid-root
                    166: (as is the case for all OpenBSD platforms).  The Xaw problem represents
                    167: a security vulnerability for any setuid-root program that uses the Xaw
                    168: library (including xterm).  Patch1 from XFree86 3.3.2 corrects
                    169: these problems.
                    170: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch>
                    171: We provide a version of this patch file specifically for the OpenBSD 2.3 tree</a>.
                    172: We also provide tar files which replace the xterm(1) binary and the libXaw
                    173: libraries on your system. These are expected to be extracted in
                    174: <strong>/usr/X11R6</strong> using the command
                    175: <strong>"tar xvfpz Xawfix.tgz"</strong>.
                    176: The files are...
                    177: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/Xawfix.tgz>i386</a>,
                    178: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/alpha/Xawfix.tgz>alpha</a>,
                    179: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mac68k/Xawfix.tgz>mac68k</a>,
                    180: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz>
                    181:        mvme68k</a>,
                    182: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/hp300/Xawfix.tgz>hp300</a>,
                    183: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/Xawfix.tgz>sparc</a>,
                    184: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz>pmax</a>,
                    185: and
                    186: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz>arc</a>.
                    187: <p>
                    188: </ul>
                    189: <a name=i386></a>
                    190: <li><h3><font color=#e00000>i386</font></h3>
                    191: <ul>
                    192: <a name=pctr></a>
                    193: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
                    194: The pctr(4) driver has bugs that permit any user to crash the machine,
                    195: if the CPU is not an Intel CPU.  This problem has been properly fixed
                    196: since, but fixes are hard to apply to the 2.2 or 2.3 releases.  To avoid
                    197: the problem, recompile your kernel without the pctr(4) device driver.
                    198: <p>
                    199: <li><font color=#009000><strong>CORRUPTED FILE</strong></font><br>
                    200: The CD version of the precompiled ghostscript package is corrupted and
                    201: not installable.  The correct file can be retrieved by FTP from:
                    202: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz>
                    203: ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz</a>.
                    204: Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and
                    205: <i>sha1(1)</i> respectively) are:
                    206: <ul>
                    207: <li>725752890 3639338 ghostscript-5.10.tgz
                    208: <li>MD5 (ghostscript-5.10.tgz) = 3144ca814ad1965d671be2b7be3d3050
                    209: <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
                    210: </ul>
                    211: <p>
                    212: <a name=pcvt></a>
                    213: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
                    214: The pcvt(4) console driver has a bug that can cause some keyboard
                    215: controllers to lock up when a key is pressed that toggles the status
                    216: of a keyboard LED (scroll lock, caps lock, etc).  The problem is
                    217: generally intermittent and the keyboard can be "unlocked" by unplugging
                    218: and plugging it back in.
                    219: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch>
                    220: A source code patch exists which remedies this problem.</a>
                    221: <p>
                    222: </ul>
                    223: <a name=mac68k></a>
                    224: <li><h3><font color=#e00000>mac68k</font></h3>
                    225: <ul>
                    226: <li>No problems identified yet.
                    227: <p>
                    228: </ul>
                    229: <a name=sparc></a>
                    230: <li><h3><font color=#e00000>sparc</font></h3>
                    231: <ul>
                    232: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
                    233: The 2.3 release does not run reliably on the sun4m LX/LC machines
                    234: (ie. Sparc Classic).
                    235: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch>
                    236: A source code patch exists which remedies this problem.</a>
                    237: Two kernels which replace the ones in the release are also provided:
                    238: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd>bsd</a> and
                    239: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3>bsd.scsi3</a>.
                    240: Other replacements for the 2.3 install tools are
                    241: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc>also available</a>.
                    242: <p>
                    243: </ul>
                    244: <a name=amiga></a>
                    245: <li><h3><font color=#e00000>amiga</font></h3>
                    246: <ul>
                    247: <li><font color=#009000><strong>MINOR INCOMPATIBILITY</strong></font><br>
                    248: The AmigaOS patch
                    249: <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>
                    250: improves AmigaOS memory handling tremendously, but confuses loadbsd, which
                    251: grabs less memory from the system than is available. To work around the
                    252: problem, be sure to execute
                    253: <pre>
                    254:     PoolMem remove
                    255: </pre>
                    256: right before running loadbsd. The next release of loadbsd will probably be
                    257: PoolMem-aware.
                    258: <p>
                    259: </ul>
                    260: <a name=pmax></a>
                    261: <li><h3><font color=#e00000>pmax</font></h3>
                    262: <ul>
                    263: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
                    264: The XFree86 binary set shipped on the CD and FTP site are not the
                    265: exact final set that we shipped for the other releases.  A few minor
                    266: changes, mostly in <strong>xdm(1)</strong> configuration, were made
                    267: after those binaries were made.  Patches for this might come out later.
                    268: <p>
                    269: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
                    270: The XFree86 binary set was linked with an older version of the C
                    271: library.  To work around the problem, do the following as root.
                    272: <p>
                    273: <ul>
                    274: cd /usr/lib/
                    275: <br>
                    276: ln -s libc.so.18.0 libc.so.17
                    277: </ul>
                    278: <p>
                    279: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
                    280: The X11R5 server used in this port does not understand the default
                    281: authorization types used by the X11R6 clients, which results in no
                    282: clients being able to connect to the  server.  To fix this
                    283: problem add the line below to /usr/X11R6/lib/X11/xdm/xdm-config.
                    284: <p>
                    285: <ul>
                    286: DisplayManager._0.authName: MIT-MAGIC-COOKIE-1
                    287: </ul>
                    288: <p>
                    289: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
                    290: The pmax install does not correctly install the boot block.
                    291: To work around the problem, after the install program has finished, do
                    292: the following (assuming scsi id 0):
                    293: <p>
                    294: <ul>
                    295: disklabel rz0 > /tmp/label
                    296: <br>
                    297: disklabel -R -B rz0 /tmp/label
                    298: </ul>
                    299: <p>
                    300: </ul>
                    301: <a name=arc></a>
                    302: <li><h3><font color=#e00000>arc</font></h3>
                    303: <ul>
                    304: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
                    305: The XFree86 binary set shipped on the CD and FTP site are not the
                    306: exact final set that we shipped for the other releases.  A few minor
                    307: changes, mostly in <strong>xdm(1)</strong> configuration, were made
                    308: after those binaries were made.  Patches for this might come out later.
                    309: <p>
                    310: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
                    311: The XFree86 binary set was linked with an older version of the C
                    312: library.  To work around the problem, do the following as root.
                    313: <p>
                    314: <ul>
                    315: cd /usr/lib/
                    316: <br>
                    317: ln -s libc.so.18.0 libc.so.17
                    318: </ul>
                    319: <p>
                    320: </ul>
                    321: <a name=alpha></a>
                    322: <li><h3><font color=#e00000>alpha</font></h3>
                    323: <ul>
                    324: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
                    325: When you start the install an upgrade option is advertised but
                    326: there really is no such option.
                    327: <p>
                    328: </ul>
                    329: <a name=hp300></a>
                    330: <li><h3><font color=#e00000>hp300</font></h3>
                    331: <ul>
                    332: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
                    333: When you start the install an upgrade option is advertised but
                    334: there really is no such option.
                    335: <p>
                    336: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
1.17      pvalchev  337: Unlabeled disks with weird geometries can panic the kernel.
1.1       deraadt   338: A fix will be made available when 2.3 is out.
                    339: <p>
                    340: </ul>
                    341: <a name=mvme68k></a>
                    342: <li><h3><font color=#e00000>mvme68k</font></h3>
                    343: <ul>
                    344: <li>No problems identified yet.
                    345: <p>
                    346: </ul>
                    347: <a name=powerpc></a>
                    348: <li><h3><font color=#e00000>powerpc</font></h3>
                    349: <ul>
                    350: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
                    351: The powerpc release shipped on the OpenBSD 2.3 CD does not contain
                    352: two late fixes applied late in the release cycle.  The
                    353: <a href=errata22.html#rmjob>rmjob</a> and
                    354: <a href=errata22.html#uucpd>uucpd</a> patches should be applied to
                    355: the system if those subsystems are used.
                    356: <p>
                    357: </ul>
1.10      deraadt   358:
                    359: </dl>
1.1       deraadt   360: <br>
                    361:
                    362: <hr>
1.13      jason     363: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.1       deraadt   364: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
                    365: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
1.8       deraadt   366: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
1.11      deraadt   367: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
1.12      deraadt   368: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
1.15      deraadt   369: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
1.16      deraadt   370: <a href=errata28.html>For 2.8 errata, please refer here</a>.<br>
1.19      deraadt   371: <a href=errata29.html>For 2.9 errata, please refer here</a>.<br>
1.21      deraadt   372: <a href=errata30.html>For 3.0 errata, please refer here</a>.<br>
1.22    ! jufi      373: <a href=errata.html>For 3.1 errata, please refer here</a>.<br>
1.12      deraadt   374:
1.1       deraadt   375: <hr>
1.9       deraadt   376: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1       deraadt   377: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.22    ! jufi      378: <br><small>$OpenBSD: errata23.html,v 1.21 2002/04/16 18:33:07 deraadt Exp $</small>
1.1       deraadt   379:
                    380: </body>
                    381: </html>