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

Annotation of www/errata28.html, Revision 1.101

1.94      bentley     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
1.81      tj          5: <title>OpenBSD 2.8 Errata</title>
1.1       deraadt     6: <meta name="description" content="the OpenBSD CD errata page">
1.79      deraadt     7: <meta name="viewport" content="width=device-width, initial-scale=1">
                      8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.83      tb          9: <link rel="canonical" href="https://www.openbsd.org/errata28.html">
1.1       deraadt    10:
1.69      deraadt    11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
1.1       deraadt    16:
1.94      bentley    17: <h2 id=OpenBSD>
1.79      deraadt    18: <a href="index.html">
1.94      bentley    19: <i>Open</i><b>BSD</b></a>
                     20: 2.8 Errata
1.81      tj         21: </h2>
1.79      deraadt    22: <hr>
1.1       deraadt    23:
1.28      deraadt    24: For errata on a certain release, click below:<br>
1.97      schwarze   25: <a href="errata20.html">2.0</a>,
1.27      deraadt    26: <a href="errata21.html">2.1</a>,
                     27: <a href="errata22.html">2.2</a>,
                     28: <a href="errata23.html">2.3</a>,
                     29: <a href="errata24.html">2.4</a>,
                     30: <a href="errata25.html">2.5</a>,
                     31: <a href="errata26.html">2.6</a>,
                     32: <a href="errata27.html">2.7</a>,
                     33: <a href="errata29.html">2.9</a>,
                     34: <a href="errata30.html">3.0</a>,
                     35: <a href="errata31.html">3.1</a>,
1.31      deraadt    36: <a href="errata32.html">3.2</a>,
1.32      david      37: <a href="errata33.html">3.3</a>,
1.37      david      38: <a href="errata34.html">3.4</a>,
1.38      miod       39: <a href="errata35.html">3.5</a>,
1.39      deraadt    40: <a href="errata36.html">3.6</a>,
1.97      schwarze   41: <br>
1.62      deraadt    42: <a href="errata37.html">3.7</a>,
1.41      deraadt    43: <a href="errata38.html">3.8</a>,
1.42      deraadt    44: <a href="errata39.html">3.9</a>,
1.43      deraadt    45: <a href="errata40.html">4.0</a>,
1.45      merdely    46: <a href="errata41.html">4.1</a>,
1.46      deraadt    47: <a href="errata42.html">4.2</a>,
1.47      deraadt    48: <a href="errata43.html">4.3</a>,
1.49      deraadt    49: <a href="errata44.html">4.4</a>,
1.50      deraadt    50: <a href="errata45.html">4.5</a>,
1.51      deraadt    51: <a href="errata46.html">4.6</a>,
1.53      deraadt    52: <a href="errata47.html">4.7</a>,
1.54      miod       53: <a href="errata48.html">4.8</a>,
1.55      nick       54: <a href="errata49.html">4.9</a>,
1.56      sthen      55: <a href="errata50.html">5.0</a>,
1.57      deraadt    56: <a href="errata51.html">5.1</a>,
1.58      deraadt    57: <a href="errata52.html">5.2</a>,
1.97      schwarze   58: <br>
1.59      deraadt    59: <a href="errata53.html">5.3</a>,
1.60      deraadt    60: <a href="errata54.html">5.4</a>,
1.68      jsg        61: <a href="errata55.html">5.5</a>,
1.72      deraadt    62: <a href="errata56.html">5.6</a>,
1.75      deraadt    63: <a href="errata57.html">5.7</a>,
1.76      deraadt    64: <a href="errata58.html">5.8</a>,
1.82      deraadt    65: <a href="errata59.html">5.9</a>,
1.85      tj         66: <a href="errata60.html">6.0</a>,
1.89      deraadt    67: <a href="errata61.html">6.1</a>,
1.91      deraadt    68: <a href="errata62.html">6.2</a>,
1.92      deraadt    69: <a href="errata63.html">6.3</a>,
1.93      deraadt    70: <a href="errata64.html">6.4</a>,
1.96      deraadt    71: <a href="errata65.html">6.5</a>,
1.98      deraadt    72: <a href="errata66.html">6.6</a>,
1.99      deraadt    73: <a href="errata67.html">6.7</a>,
1.100     deraadt    74: <a href="errata68.html">6.8</a>,
1.101   ! tj         75: <br>
1.100     deraadt    76: <a href="errata69.html">6.9</a>.
1.1       deraadt    77: <hr>
                     78:
1.63      deraadt    79: <p>
1.85      tj         80: Patches for the OpenBSD base system are distributed as unified diffs.
                     81: Each patch contains usage instructions.
                     82: All the following patches are also available in one
                     83: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8.tar.gz">tar.gz file</a>
                     84: for convenience.
1.1       deraadt    85:
                     86: <p>
1.85      tj         87: Patches for supported releases are also incorporated into the
1.86      tj         88: <a href="stable.html">-stable branch</a>.
1.63      deraadt    89:
1.1       deraadt    90: <hr>
                     91:
                     92: <ul>
1.95      deraadt    93:
                     94: <li id="zsconsole">
                     95: <strong>001: RELIABILITY FIX: Nov 10, 2000</strong><br>
                     96: When running a sparc with a serial console, certain types of interrupts would
                     97: cause great grief.<br>
                     98: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/001_zsconsole.patch">
                     99: A source code patch exists which remedies this problem.</a>
                    100: <p>
                    101:
                    102: <li id="skey">
                    103: <strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong>
1.66      deraadt   104: &nbsp; <i>All architectures</i><br>
1.95      deraadt   105: In ssh(1), skey support for SSH1 protocol was broken.  Some people might consider
                    106: that kind of important.<br>
                    107: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/002_sshskey.patch">
1.63      deraadt   108: A source code patch exists which remedies this problem.</a>
1.18      millert   109: <p>
1.95      deraadt   110:
                    111: <li id="qe">
                    112: <strong>003: RELIABILITY FIX: Nov 17, 2000</strong><br>
                    113: Configuring a qec+qe causes a NMI panic.<br>
                    114: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/003_qe.patch">
1.63      deraadt   115: A source code patch exists which remedies this problem.</a>
1.17      millert   116: <p>
1.95      deraadt   117:
                    118: <li id="rijndael">
                    119: <strong>004: RELIABILITY FIX: Nov 17, 2000</strong>
1.66      deraadt   120: &nbsp; <i>All architectures</i><br>
1.95      deraadt   121: First off, AES (Rijndael) encryption and decryption were broken for IPsec
                    122: and swap encryption.<br>
                    123: Secondly, the AES code did not work properly on big endian machines.<br>
                    124: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/004_rijndael.patch">
1.63      deraadt   125: A source code patch exists which remedies this problem.</a>
1.95      deraadt   126: This is the second revision of the patch.
1.14      millert   127: <p>
1.95      deraadt   128:
                    129: <li id="ftpd">
                    130: <strong>005: SECURITY FIX: Dec 4, 2000</strong>
1.66      deraadt   131: &nbsp; <i>All architectures</i><br>
1.95      deraadt   132: OpenBSD 2.8's ftpd contains a one-byte overflow in the replydirname() function.<br>
                    133: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/005_ftpd.patch">
1.63      deraadt   134: A source code patch exists which remedies this problem.</a>
1.95      deraadt   135: You can view the <a href="advisories/ftpd_replydirname.txt">OpenBSD Advisory</a> here.
                    136: <p>
                    137:
                    138: <li id="pcibios">
                    139: <strong>006: STABILITY FIX: Dec 4, 2000</strong><br>
                    140: On some machines, a PCIBIOS device driver interrupt allocation bug can cause a
                    141: kernel hang while probing PCI devices.  If you have this symptom, you can disable
                    142: PCIBIOS as a workaround.  To do this,
                    143:     <ul>
                    144:     <li>Enter the User Kernel Configuration by booting with the
                    145:        option &quot;boot -c&quot;.
                    146:     <li>Once at the <i>UKC></i> prompt, enter
                    147:         <blockquote><pre>
                    148:        UKC> disable pcibios
                    149:        UKC> quit<!--
                    150:        --></pre></blockquote>
                    151:     <li>See <a href="./faq/faq5.html#5.6">this page</a> after a successful
                    152:     boot for instructions on how to re-write your kernel to disable PCIBIOS
                    153:     permanently.
                    154:     </ul>
1.10      aaron     155: <p>
1.95      deraadt   156:
                    157: <li id="x_sun3">
                    158: <strong>007: INSTALL PROBLEM: Dec 4, 2000</strong><br>
                    159: The X packages
                    160: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xshare28.tgz">share28.tgz</a>
                    161: and
                    162: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xfont28.tgz">font28.tgz</a>
                    163: were not on the CD, and only available via FTP install.  These packages can be
                    164: added post-install by using the following command:
                    165: <pre>
                    166:     # cd /; tar xvfpz xshare28.tgz
                    167:     # cd /; tar xvfpz xfont28.tgz
                    168: </pre>
                    169: <p>
                    170:
                    171: <li id="kerberos">
                    172: <strong>008: SECURITY FIX: Dec 7, 2000</strong>
1.66      deraadt   173: &nbsp; <i>All architectures</i><br>
1.95      deraadt   174: Two problems have recently been discovered in the KerberosIV code.<p>
                    175: 1. A symlink problem was discovered in the KerberosIV password checking
                    176: routines /usr/bin/su and /usr/bin/login, which makes it possible for a
                    177: local user to overwrite any file on the local machine.<p>
                    178: 2. It is possible to specify environment variables in telnet
                    179: which will be passed over the to the remote host. This makes it
                    180: possible to set environment variables on the remote side, including
                    181: ones that have special meaning on the server. It is not clear at this
                    182: time what the impact is, but we recommend everyone to upgrade their
                    183: machines immediately.<p>
                    184: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/008_kerberos.patch">
1.63      deraadt   185: A source code patch exists which remedies this problem.</a>
1.4       millert   186: <p>
1.95      deraadt   187:
                    188: <li id="kerberos2">
                    189: <strong>009: SECURITY FIX: Dec 10, 2000</strong>
1.66      deraadt   190: &nbsp; <i>All architectures</i><br>
1.95      deraadt   191: Another problem exists in the Kerberos libraries.<br>
                    192: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/009_kerberos2.patch">
1.63      deraadt   193: A source code patch exists which remedies this problem.</a>
1.3       millert   194: <p>
1.95      deraadt   195:
                    196: <li id="fastroute">
                    197: <strong>010: RELIABILITY FIX: Dec 11, 2000</strong>
1.66      deraadt   198: &nbsp; <i>All architectures</i><br>
1.95      deraadt   199: A crash could occur during fast routing, if IPSEC was enabled.<br>
                    200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/010_fastroute.patch">
1.63      deraadt   201: A source code patch exists which remedies this problem.</a>
1.1       deraadt   202: <p>
1.95      deraadt   203:
                    204: <li id="hwcrypto">
                    205: <strong>011: RELIABILITY FIX: Dec 13, 2000</strong>
1.66      deraadt   206: &nbsp; <i>All architectures</i><br>
1.95      deraadt   207: The crypto subsystem could incorrectly fail to run certain software ciphers,
                    208: if a hardware card existed in the machine.<br>
                    209: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/011_hwcrypto.patch">
1.63      deraadt   210: A source code patch exists which remedies this problem.</a>
1.1       deraadt   211: <p>
1.95      deraadt   212:
                    213: <li id="imacdv">
                    214: <strong>012: INSTALL PROBLEM: Dec 14, 2000</strong><br>
                    215: The IMac DV+ (and probably some other machines) incorrectly identify their video
                    216: hardware, but it is possible to work around the problem.<br>
                    217: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/012_imacdv.patch">
1.63      deraadt   218: A source code patch exists which remedies this problem.</a>
1.1       deraadt   219: <p>
1.95      deraadt   220:
                    221: <li id="procfs">
                    222: <strong>013: SECURITY FIX: Dec 18, 2000</strong>
1.66      deraadt   223: &nbsp; <i>All architectures</i><br>
1.95      deraadt   224: <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>
                    225: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/013_procfs.patch">
1.63      deraadt   226: A source code patch exists which remedies this problem.</a>
1.1       deraadt   227: <p>
1.95      deraadt   228:
                    229: <li id="xlock">
                    230: <strong>014: SECURITY FIX: Dec 22, 2000</strong>
1.66      deraadt   231: &nbsp; <i>All architectures</i><br>
1.95      deraadt   232: 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>
                    233: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/014_xlock.patch">
1.63      deraadt   234: A source code patch exists which remedies this problem.</a>
1.1       deraadt   235: <p>
1.95      deraadt   236: 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>
                    237:  and <i>chmod 4755 /usr/X11R6/bin/xlock</i>.
                    238: <p>
                    239: <ul>
                    240: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/xlock">Xlock - i386</a>
                    241: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/xlock">Xlock - sparc</a>
                    242: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mac68k/xlock">Xlock - mac68k</a>
                    243: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/xlock">Xlock - powerpc</a>
                    244: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/amiga/xlock">Xlock - amiga</a>
                    245: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/hp300/xlock">Xlock - hp300</a>
                    246: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mvme68k/xlock">Xlock - mvme68k</a>
                    247: </ul>
1.65      deraadt   248: <p>
1.95      deraadt   249:
                    250: <li id="pms">
                    251: <strong>015: STABILITY FIX: Dec 22, 2000</strong><br>
                    252: Some machines locked up while trying to use the mouse in console mode. This patch solves that problem.<br>
                    253: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/015_pms.patch">
1.63      deraadt   254: A source code patch exists which remedies this problem.</a>
1.1       deraadt   255: <p>
1.95      deraadt   256:
                    257: <li id="tl">
                    258: <strong>016: RELIABILITY FIX: Jan 4, 2001</strong>
1.66      deraadt   259: &nbsp; <i>All architectures</i><br>
1.95      deraadt   260: Allow ThunderLAN cards to share interrupts nicely.<br>
                    261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/016_tl.patch">
1.63      deraadt   262: A source code patch exists which remedies this problem.</a>
1.1       deraadt   263: <p>
1.95      deraadt   264:
                    265: <li id="rnd">
                    266: <strong>017: SECURITY FIX: Jan 22, 2001</strong>
1.66      deraadt   267: &nbsp; <i>All architectures</i><br>
1.95      deraadt   268: 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>
                    269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/017_rnd.patch">
1.63      deraadt   270: A source code patch exists which remedies this problem.</a>
1.1       deraadt   271: <p>
1.95      deraadt   272:
1.70      bentley   273: <li id="named">
1.94      bentley   274: <strong>018: SECURITY FIX: Jan 29, 2001</strong>
1.66      deraadt   275: &nbsp; <i>All architectures</i><br>
1.88      tb        276: Merge <a href="https://man.openbsd.org/OpenBSD-2.8/named.8">named</a>
1.1       deraadt   277: with ISC BIND 4.9.8-REL, which fixes some buffer vulnerabilities (actually it appears
1.13      jsyn      278: that these were already impossible to exploit beforehand).<br>
1.84      tb        279: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/018_named.patch">
1.63      deraadt   280: A source code patch exists which remedies this problem.</a>
1.1       deraadt   281: <p>
1.95      deraadt   282:
                    283: <li id="lepci">
                    284: <strong>019: IMPLEMENTATION FIX: Jan 31, 2001</strong>
1.66      deraadt   285: &nbsp; <i>All architectures</i><br>
1.95      deraadt   286: 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>
                    287: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/019_lepci.patch">
1.63      deraadt   288: A source code patch exists which remedies this problem.</a>
1.1       deraadt   289: <p>
1.95      deraadt   290:
                    291: <li id="libwrap">
                    292: <strong>020: IMPLEMENTATION FIX: Feb 15, 2001</strong>
1.66      deraadt   293: &nbsp; <i>All architectures</i><br>
1.95      deraadt   294: 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>
                    295: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/020_libwrap.patch">
1.63      deraadt   296: A source code patch exists which remedies this problem.</a>
1.1       deraadt   297: <p>
1.95      deraadt   298:
                    299: <li id="sudo">
                    300: <strong>021: SECURITY FIX: Feb 22, 2001</strong>
                    301: &nbsp; <i>All architectures</i><br>
                    302: There is an exploitable heap corruption bug in
                    303: <a href="https://man.openbsd.org/OpenBSD-2.8/sudo.8">sudo</a>.
                    304: <br>
                    305: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/021_sudo.patch">
1.65      deraadt   306: A source code patch exists which remedies this problem.</a>
                    307: <p>
1.95      deraadt   308:
                    309: <li id="userldt">
                    310: <strong>022: SECURITY FIX: Mar 2, 2001</strong><br>
                    311: 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.
                    312: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/022_userltd.patch">
1.63      deraadt   313: A source code patch exists which remedies this problem.</a>
1.1       deraadt   314: <p>
1.95      deraadt   315:
                    316: <li id="ipsec_ah">
                    317: <strong>023: SECURITY FIX: Mar 2, 2001</strong>
1.66      deraadt   318: &nbsp; <i>All architectures</i><br>
1.95      deraadt   319: 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>
                    320: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/023_ip_ah.patch">
1.63      deraadt   321: A source code patch exists which remedies this problem.</a>
1.1       deraadt   322: <p>
1.95      deraadt   323:
                    324: <li id="readline">
                    325: <strong>024: SECURITY FIX: Mar 18, 2001</strong>
                    326: &nbsp; <i>All architectures</i><br>
                    327: The readline library shipped with OpenBSD allows history files creation
                    328: with a permissive
                    329: <a href="https://man.openbsd.org/OpenBSD-2.8/umask.2">umask(2)</a>.
                    330: This can lead to the leakage of sensitive information in applications
                    331: that use passwords and the like during user interaction (one such
                    332: application is mysql).<br>
                    333: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/024_readline.patch">
1.65      deraadt   334: A source code patch exists which remedies this problem.</a>
                    335: <p>
1.95      deraadt   336:
                    337: <li id="glob">
                    338: <strong>025: SECURITY FIX: Apr 10, 2001</strong>
1.66      deraadt   339: &nbsp; <i>All architectures</i><br>
1.95      deraadt   340: <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a> contains multiple buffer overflows. <br>
                    341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/025_glob.patch">
1.63      deraadt   342: A source code patch exists which remedies this problem.</a>
1.1       deraadt   343: <p>
1.95      deraadt   344:
                    345: <li id="glob_limit">
                    346: <strong>026: SECURITY FIX: Apr 23, 2001</strong>
1.66      deraadt   347: &nbsp; <i>All architectures</i><br>
1.95      deraadt   348: <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>
                    349: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/026_globlimit.patch">
1.63      deraadt   350: A source code patch exists which remedies this problem.</a>
1.1       deraadt   351: <p>
1.95      deraadt   352:
                    353: <li id="ipf_frag">
                    354: <strong>027: SECURITY FIX: Apr 23, 2001</strong>
1.66      deraadt   355: &nbsp; <i>All architectures</i><br>
1.95      deraadt   356: IPF has a serious problem with fragment caching, the bug is triggered if you use the ipf(5) syntax &quot;keep state&quot;.<br>
                    357: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/027_ipf-frag.patch">
1.63      deraadt   358: A source code patch exists which remedies this problem.</a>
1.1       deraadt   359: <p>
1.95      deraadt   360:
                    361: <li id="sendmail">
                    362: <strong>028: SECURITY FIX: May 29, 2001</strong>
1.66      deraadt   363: &nbsp; <i>All architectures</i><br>
1.95      deraadt   364: 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
                    365: context of a signal handler.  This leads to potentially serious
                    366: race conditions.  At the moment this is a theoretical attack only
                    367: and can only be exploited on the local host (if at all).<br>
                    368: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/028_sendmail.patch">
1.63      deraadt   369: A source code patch exists which remedies this problem.</a>
1.95      deraadt   370: It updates sendmail to version 8.11.4.
1.1       deraadt   371: <p>
1.95      deraadt   372:
                    373: <li id="fts">
                    374: <strong>029: SECURITY FIX: May 30, 2001</strong>
1.66      deraadt   375: &nbsp; <i>All architectures</i><br>
1.95      deraadt   376: Programs using the <a href="https://man.openbsd.org/OpenBSD-2.8/fts.3">fts(3)</a>
                    377: routines (such as rm, find, and most programs that take a <b>-R</b>
                    378: flag) can be tricked into changing into the wrong directory if the
                    379: parent dir is changed out from underneath it.  This is similar to
                    380: the old fts bug but happens when popping out of directories, as
                    381: opposed to descending into them.
                    382: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/029_fts.patch">
1.65      deraadt   383: A source code patch exists which remedies this problem.</a>
1.95      deraadt   384: This is the second version of the patch.
1.1       deraadt   385: <p>
1.95      deraadt   386:
                    387: <li id="kernexec">
                    388: <strong>030: SECURITY FIX: June 15, 2001</strong>
1.66      deraadt   389: &nbsp; <i>All architectures</i><br>
1.95      deraadt   390: 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.
                    391: <br>
                    392: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/030_kernexec.patch">
1.65      deraadt   393: A source code patch exists which remedies this problem.</a>
1.1       deraadt   394: <p>
1.95      deraadt   395:
                    396: <li id="sendmail2">
                    397: <strong>031: SECURITY FIX: August 21, 2001</strong>
                    398: &nbsp; <i>All architectures</i><br>
                    399: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a>
                    400: that may allow an attacker on the local host to gain root privileges by
                    401: specifying out-of-bounds debug parameters.
                    402: <br>
                    403: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/031_sendmail.patch">
1.1       deraadt   404: A source code patch exists which remedies this problem.</a>
                    405: <p>
1.95      deraadt   406:
                    407: <li id="lpd">
                    408: <strong>032: SECURITY FIX: August 29, 2001</strong>
1.66      deraadt   409: &nbsp; <i>All architectures</i><br>
1.95      deraadt   410: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/lpd.8">lpd(8)</a>
                    411: that may allow an attacker with line printer access to gain root
                    412: privileges.  A machine must be running lpd to be vulnerable (OpenBSD
                    413: does not start lpd by default).  Only machines with line printer
                    414: access (ie: listed in either /etc/hosts.lpd or /etc/hosts.equiv)
                    415: may be used to mount an attack.
                    416: <br>
                    417: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/032_lpd.patch">
1.65      deraadt   418: A source code patch exists which remedies this problem.</a>
                    419: <p>
1.95      deraadt   420:
                    421: <li id="uucp">
                    422: <strong>033: SECURITY FIX: September 11, 2001</strong>
                    423: &nbsp; <i>All architectures</i><br>
                    424: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/uuxqt.8">uuxqt(8)</a>
                    425: that may allow an attacker to run arbitrary commands as user uucp and
                    426: use this to gain root access.
                    427: The UUCP execution daemon, uuxqt(8), has a bug in its command line
                    428: parsing routine may allow arbitrary commands to be run.  Because
                    429: some UUCP commands are run as root (and daemon) from cron it is possible
                    430: to leverage compromise of the UUCP user to gain root.
                    431: <br>
                    432: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/033_uucp.patch">
1.1       deraadt   433: A source code patch exists which remedies this problem.</a>
                    434: <p>
1.82      deraadt   435:
1.1       deraadt   436: </ul>
1.61      deraadt   437:
1.71      tedu      438: <hr>