Annotation of www/errata22.html, Revision 1.10
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD release errata</title>
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">
10: <meta name="copyright" content="This document copyright 1997 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
1.10 ! pauls 15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.1 deraadt 16: <h2><font color=#0000e0>
17: This is the OpenBSD 2.2 release errata & patch list:
18: </font></h2>
19:
1.2 deraadt 20: <hr>
21: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
22: <a href=errata.html>For 2.3 errata, please refer here</a>.<br>
23: <hr>
24:
1.1 deraadt 25: <ul>
26: <a name=all></a>
27: <li><h3><font color=#e00000>All architectures</font></h3>
28: <ul>
1.9 deraadt 29: <a name=ipsec></a>
1.5 matthieu 30: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.7 deraadt 31: If IPSEC communication is attempted by starting photurisd(8) (which is
1.8 deraadt 32: disabled by default), a system crash may be evoked from remote if
33: an attacker uses some classes of invalid packets.
1.7 deraadt 34: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>
35: A source code patch exists which remedies this problem.</a>
1.9 deraadt 36: <p>
37: <a name=xterm-xaw></a>
1.7 deraadt 38: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.5 matthieu 39: As stated in CERT advisory VB-98.04, there are buffer
1.8 deraadt 40: overrun problems in <strong>xterm</strong> related to the input-Method,
41: preeditType, and *Keymap resources. Additional buffer overruns exist in
42: the <strong>Xaw</strong> library related to the inputMethod and
43: preeditType resources. The xterm(1) problem represents a security
44: vulnerability for any platform where xterm is installed setuid-root
45: (as is the case for all OpenBSD platforms). The Xaw problem represents
46: a security vulnerability for any setuid-root program that uses the Xaw
47: library (including xterm). Patch1 from XFree86 3.3.2 corrects
48: these problems.
1.5 matthieu 49: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/xterm-xaw.patch>
1.6 deraadt 50: We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
1.5 matthieu 51: <p>
1.1 deraadt 52: <a name=rmjob></a>
53: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
54: An exploitable buffer mismanagement exists in a subroutine used by
55: lprm and lpd. The problem is exploitable by users on a particular
56: machine if there is an entry in <strong>/etc/printcap</strong> which
57: points at a remote printer.
58: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch>
59: A patch is available which corrects this behaviour</a>.
60: <p>
61: <a name=uucpd></a>
62: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
63: A DNS-based vulnerability exists when uucpd is used. By default uucpd
64: is not enabled in the OpenBSD releases, but some sites may have enabled it.
65: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch>
66: A patch is available which corrects this behaviour</a>.
67: <p>
68: <a name=named></a>
69: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
70: A vulnerability exists when (and only when) /etc/named.conf has the
71: <strong>fake-iquery</strong> option enabled.
72: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch>
73: A patch is available which corrects this behaviour</a>.
74: <p>
75: <a name=ping></a>
76: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
77: A vulnerability exists in ping(8); if the -R option is used to record
78: routes, an attacker can spoof a reply packet that will overflow inside
79: ping. Preliminary investigation makes it look the worst attack
80: possible is to make ping crash, but one never knows...
81: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch>
82: A patch is available which corrects this behaviour</a>.
83: <p>
84: <a name=sourceroute></a>
85: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
86: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
87: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
88: is disabled (value 0), the kernel will block source routed packets from
89: going through, but will still accept source routing packets destined for
90: itself. Our fix changes the <strong>net.inet.ip.sourceroute</strong>
91: variable semantics to mean that all source routed packets should
92: be blocked completely.
93: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch>
94: A kernel patch is provided</a>.
95: <p>
96: <a name=ruserok></a>
97: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
98: A combination localhost+remote host security problem exists if a
99: local user running a setuid binary causes a non-existant root .rhosts
100: file to be created via a symbolic link with a specific kind of corefile,
101: and then subsequently uses rsh/rlogin to enter the machine from remote.
102: A similar exploit might also be possible using sshd which lacks any code
103: for checking for deviations from the expected format in the .rhosts or
104: .shosts files, but we have not confirmed this yet. The following two
105: fixes are recommended:
106: <p>
107: <ul>
108: <li>
109: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch>
110: (1) A kernel patch which adds a new sysctl option which permits the
111: administrator to decide whether setuid corefiles should be written or not</a>.
112: <p>
113: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch>
114: (2) Replaces the libc ruserok() function with a more paranoid
115: version which detects bogus looking .rhosts files better.</a>
116: </ul>
117: <p>
118: If the
119: first patch is used to stop setuid coredumps, then the second patch is
120: not as important.
121: This problem is fixed much better in OpenBSD-current, where the kernel's
122: symbolic link handling has been improved such that coredumping will not
123: create a file on the other side of a symbolic link. Such a patch is not
124: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
125: The problem with the ruserok() function appears to also exist in
126: ssh 1.2.21 and previous (the ssh people have been alerted).
127: <p>
128: <a name=mmap></a>
129: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
130: A bug in the vm system permits a file descriptor opened read-only on a
131: device, to later on be mmap(2)'d read-write, and then modified. This
132: does not result in a security hole by itself, but it does violate the
133: safety semantics which securelevels are supposed to provide. If a user
134: manages to gain kmem group permissions, using this problem they can then
135: gain root trivially and/or turn securelevels off.
136: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch>
137: A kernel patch is available which corrects this behaviour (this is
138: revision 3 of this patch)</a>.
139: <p>
140: <li><font color=#009000><strong>BUILD PROCESS FIX</strong></font><br>
141: Building an object tree from a read-only source tree (such as off a CDROM)
142: may fail under certain circumstances (e.g. when creating a symlink on sparc
143: whose target name is exactly 33 characters). As a workaround you have to
144: either provide the source tree read/write, or install a newer version of
145: /usr/bin/readlink.
146: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c>
147: A replacement source file exists</a>.
148: <p>
149: <a name=mountd></a>
150: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
151: If a line in /etc/exports which contains hostnames results in an empty
152: list because none of the supplied hostnames is known, mountd(8) will
153: accidentally export the filesystem to the world.
154: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch>
155: A patch is available which corrects this behaviour</a>.
156: <p>
157: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
158: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
159: system calls could cause a kernel panic.
160: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch>
161: A patch</a> to return EINVAL in this case is available.
162: <p>
163: </ul>
164: <a name=i386></a>
165: <li><h3><font color=#e00000>i386</font></h3>
166: <ul>
167: <a name=f00f></a>
168: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
169: The Intel P5 F00F bug was discovered after the CDR's had already been
170: sent to the manufacturer. This problem permits any user who has an account
171: to lock your machine up using a 4-line program. The problem only affects
172: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
173: nor are processors by other manufacturers).
174: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch>
175: A kernel source-code patch is available</a>.
176: <p>
177: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
178: Some Linux binaries will execute in SVR4 emulation mode, which is
179: definately a problem for people who need Linux emulation to work correctly.
180: To solve this mis-identification problem,
181: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
182: a patch file is provided</a>.
183: <p>
184: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
185: APM can crash on machines without it.
186: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch>
187: A kernel source-code patch is available</a>.
188: <p>
189: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
190: A few people are running into this problem, particularily if they had some
191: other *BSD operating system on their machine before trying OpenBSD: if after
192: installation onto an IDE-based machine, the kernel fails to mount the root
193: partition because it thinks that it should be opening sd0 (0x400), this means
194: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
195: is indicating that the drive is SCSI.
196: To repair this, use the floppy to run "disklabel -E wd0", then using the
197: "edit" command ensure the type field is set to "ST506".
198: <p>
199: </ul>
200: <a name=mac68k></a>
201: <li><h3><font color=#e00000>mac68k</font></h3>
202: <ul>
203: <li><font color=#009000><strong>NEW SOFTWARE</strong></font><br>
204: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
205: CDROM. However, X11 for the mac68k is immediately available from
206: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
207: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please
208: be sure to read the <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing
209: and setting up X.
210: <p>
211: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
212: As shipped on the CDROM, both the
213: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
214: generic kernel</a>
215: and the
216: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
217: genericsbc kernel</a>
218: extract themselves into the wrong place in the filesystem.
219: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
220: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
221: <p>
222: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
223: fresh kernels are available from <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
224: ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>. If at all possible,
225: installing these kernels is recommended.
226: <p>
227: A number of possible workarounds exist if you don't have easy access to ftp
228: the updated kernels. The simplest of these is to use a
229: MacOS program to uncompress and untar the kernel aad use the Installer's
230: mini-shell to "cpin" the kernel. Alternately, you could install the kernel
231: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
232: <p>
233: </ul>
234: <a name=sparc></a>
235: <li><h3><font color=#e00000>sparc</font></h3>
236: <ul>
237: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
238: Older 4/xxx systems (particularily the 4/300's) cannot boot
239: with the 2.2 kernel due to bugs in the scsi device driver.
240: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch>
241: A kernel source patch is available</a>.
242: Replacement kernels are available for:
243: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,
244: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,
245: and a replacement for bsd.rd is coming soon.
246: <p>
247: <a name=sparciommu></a>
248: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
249: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
250: using a custom kernel configured for option sun4m only.
251: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch>
252: A workaround (kernel source patch) is available</a>. Apply the patch and
253: then re-build your kernel.
254: <p>
255: </ul>
256: <li><h3><font color=#e00000>amiga</font></h3>
257: <p>
258: <ul>
259: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
260: Missing Xamiga manual pages. Get
261: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz>
262: this package</a> and execute, <i>as root</i>:<br>
263: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
264: The MD5 checksum of this package is:<br>
265: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
266: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
267: The Ariadne ethernet support was broken, there will be both binary and
268: source level fixes available shortly. If you are in a hurry mail
269: <a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.<p>
270: </ul>
271: <a name=pmax></a>
272: <li><h3><font color=#e00000>pmax</font></h3>
273: <ul>
274: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
275: There is a Year-1998 problem in the time-setting code (which causes the
276: date and time to be set incorrectly after a reboot in 1998).
277: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch>
278: A source code patch file is available</a> plus replacement installation
279: kernels for the 2.2 release at
280: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,
281: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,
282: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.
283: <p>
284: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
285: X11 support for the 3min and 3maxplus machines was broken
286: due to a kernel bug.
287: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch>
288: A source code patch is available</a>.
289: <p>
290: <a name=ldso></a>
291: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
292: A security problem in the shared library linker <strong>ld.so</strong>
293: requires that you replace it with a new binary. The following binary
294: will work on both pmax and arc machines.
295: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
296: The replacement binary is here</a>.
297: <p>
298: </ul>
299: <a name=arc></a>
300: <li><h3><font color=#e00000>arc</font></h3>
301: <ul>
302: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
303: A security problem in the shared library linker <strong>ld.so</strong> requires
304: that you replace it with a new binary. The following binary
305: will work on both pmax and arc machines.
306: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
307: The replacement binary is here</a>.
308: <p>
309: </ul>
310: <li><h3><font color=#e00000>alpha</font></h3>
311: <p>
312: <ul>
313: <li><font color=#009000><strong>MISSING FUNCTIONALITY</strong></font><br>
1.4 deraadt 314: Network Address Translation and other parts of IP Filtering do not work
1.1 deraadt 315: on the alpha. This will be fixed in the 2.3 release, and perhaps earlier
316: in a snapshot. There is no patch for 2.2.
317: <p>
318: </ul>
319: <li><h3><font color=#e00000>hp300</font></h3>
320: <p>
321: <ul>
322: <li>No problems identified yet.
323: <p>
324: </ul>
325: <li><h3><font color=#e00000>mvme68k</font></h3>
326: <ul>
327: <li>No problems identified yet.
328: <p>
329: </ul>
330: </ul>
331: <br>
332:
333: <hr>
1.3 deraadt 334: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
335: <a href=errata.html>For 2.3 errata, please refer here</a>.<br>
1.1 deraadt 336: <hr>
1.2 deraadt 337:
1.10 ! pauls 338: <a href=orders.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 339: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.10 ! pauls 340: <br><small>$OpenBSD: errata22.html,v 1.9 1998/05/06 14:28:44 deraadt Exp $</small>
1.1 deraadt 341:
342: </body>
343: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata22.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www