Annotation of www/security.html, Revision 1.187
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.20 deraadt 4: <title>OpenBSD Security</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="OpenBSD advisories">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
1.182 horacio 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">
1.77 deraadt 14: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.106 deraadt 15: <p>
1.110 deraadt 16: <h2><font color=#e00000>Security</font><hr></h2>
1.1 deraadt 17:
1.114 philen 18: <table width="100%">
19: <tr>
20: <td colspan="2">
21: <strong>Index</strong>
22: </td>
23: </tr>
24: <tr>
25: <td valign="top">
1.106 deraadt 26: <a href=#goals>Security goals of the Project</a>.<br>
27: <a href=#disclosure>Full Disclosure policy</a>.<br>
28: <a href=#process>Source code auditing process</a>.<br>
1.111 aaron 29: <a href=#default>"Secure by Default"</a>.<br>
1.106 deraadt 30: <a href=#crypto>Use of Cryptography</a>.<br>
31: <p>
32: <a href=#watching>Watching changes</a>.<br>
33: <a href=#reporting>Reporting security issues</a>.<br>
1.107 deraadt 34: <a href=#papers>Further Reading</a><br>
1.106 deraadt 35: <p>
1.114 philen 36: </td>
37: <td valign="top">
1.187 ! deraadt 38: <a href="#30">For 3.0 security advisories</a>.<br>
1.173 deraadt 39: <a href="#29">For 2.9 security advisories</a>.<br>
1.152 deraadt 40: <a href="#28">For 2.8 security advisories</a>.<br>
1.124 deraadt 41: <a href="#27">For 2.7 security advisories</a>.<br>
1.119 deraadt 42: <a href="#26">For 2.6 security advisories</a>.<br>
1.114 philen 43: <a href="#25">For 2.5 security advisories</a>.<br>
44: <a href="#24">For 2.4 security advisories</a>.<br>
45: <a href="#23">For 2.3 security advisories</a>.<br>
46: <a href="#22">For 2.2 security advisories</a>.<br>
47: <a href="#21">For 2.1 security advisories</a>.<br>
48: <a href="#20">For 2.0 security advisories</a>.<br>
49: </td>
50: </tr>
51: </table>
1.56 deraadt 52: <hr>
53:
1.106 deraadt 54: <dl>
55: <a name=goals></a>
1.110 deraadt 56: <li><h3><font color=#e00000>Goal</font></h3><p>
1.22 deraadt 57:
1.14 deraadt 58: OpenBSD believes in strong security. Our aspiration is to be NUMBER
1.22 deraadt 59: ONE in the industry for security (if we are not already there). Our
60: open software development model permits us to take a more
61: uncompromising view towards increased security than Sun, SGI, IBM, HP,
62: or other vendors are able to. We can make changes the vendors would
1.27 deraadt 63: not make. Also, since OpenBSD is exported with <a href=crypto.html>
1.45 deraadt 64: cryptography</a>, we are able to take cryptographic approaches towards
65: fixing security problems.<p>
1.18 deraadt 66:
1.106 deraadt 67: <a name=disclosure></a>
1.110 deraadt 68: <li><h3><font color=#e00000>Full Disclosure</font></h3><p>
1.106 deraadt 69:
1.45 deraadt 70: Like many readers of the
1.102 deraadt 71: <a href=http://www.securityfocus.com/bugtraq/archive>
1.18 deraadt 72: BUGTRAQ mailing list</a>,
1.106 deraadt 73: we believe in full disclosure of security problems. In the
74: operating system arena, we were probably the first to embrace
75: the concept. Many vendors, even of free software, still try
76: to hide issues from their users.<p>
77:
78: Security information moves very fast in cracker circles. On the other
79: hand, our experience is that coding and releasing of proper security
80: fixes typically requires about an hour of work -- very fast fix
81: turnaround is possible. Thus we think that full disclosure helps the
82: people who really care about security.<p>
83:
1.153 jufi 84: <a name=process></a>
1.110 deraadt 85: <li><h3><font color=#e00000>Audit Process</font></h3><p>
1.15 deraadt 86:
1.12 deraadt 87: Our security auditing team typically has between six and twelve
1.45 deraadt 88: members who continue to search for and fix new security holes. We
89: have been auditing since the summer of 1996. The process we follow to
90: increase security is simply a comprehensive file-by-file analysis of
1.106 deraadt 91: every critical software component. We are not so much looking for
92: security holes, as we are looking for basic software bugs, and if
1.138 deraadt 93: years later someone discovers the problem used to be a security
1.106 deraadt 94: issue, and we fixed it because it was just a bug, well, all the
95: better. Flaws have been found in just about every area of the system.
96: Entire new classes of security problems have been found during our
97: audit, and often source code which had been audited earlier needs
98: re-auditing with these new flaws in mind. Code often gets audited
99: multiple times, and by multiple people with different auditing
100: skills.<p>
1.12 deraadt 101:
1.94 deraadt 102: Some members of our security auditing team worked for Secure Networks,
103: the company that made the industry's premier network security scanning
104: software package Ballista (Secure Networks got purchased by Network
105: Associates, Ballista got renamed to Cybercop Scanner, and well...)
106: That company did a lot of security research, and thus fit in well
1.106 deraadt 107: with the OpenBSD stance. OpenBSD passed Ballista's tests with flying
108: colours since day 1.<p>
1.31 deraadt 109:
1.34 deraadt 110: Another facet of our security auditing process is its proactiveness.
1.45 deraadt 111: In most cases we have found that the determination of exploitability
112: is not an issue. During our ongoing auditing process we find many
113: bugs, and endeavor to fix them even though exploitability is not
114: proven. We fix the bug, and we move on to find other bugs to fix. We
115: have fixed many simple and obvious careless programming errors in code
116: and only months later discovered that the problems were in fact
117: exploitable. (Or, more likely someone on
1.102 deraadt 118: <a href=http://www.securityfocus.com/bugtraq/archive>BUGTRAQ</a>
1.45 deraadt 119: would report that other operating systems were vulnerable to a `newly
120: discovered problem', and then it would be discovered that OpenBSD had
121: been fixed in a previous release). In other cases we have been saved
122: from full exploitability of complex step-by-step attacks because we
123: had fixed one of the intermediate steps. An example of where we
1.94 deraadt 124: managed such a success is the lpd advisory that Secure Networks put out.
125: <p>
1.29 deraadt 126:
1.110 deraadt 127: <li><h3><font color=#e00000>The Reward</font></h3><p>
1.106 deraadt 128:
1.45 deraadt 129: Our proactive auditing process has really paid off. Statements like
1.35 deraadt 130: ``This problem was fixed in OpenBSD about 6 months ago'' have become
1.45 deraadt 131: commonplace in security forums like
1.102 deraadt 132: <a href=http://www.securityfocus.com/bugtraq/archive>BUGTRAQ</a>.<p>
1.35 deraadt 133:
1.45 deraadt 134: The most intense part of our security auditing happened immediately
1.80 espie 135: before the OpenBSD 2.0 release and during the 2.0->2.1 transition,
1.45 deraadt 136: over the last third of 1996 and first half of 1997. Thousands (yes,
137: thousands) of security issues were fixed rapidly over this year-long
138: period; bugs like the standard buffer overflows, protocol
139: implementation weaknesses, information gathering, and filesystem
140: races. Hence most of the security problems that we encountered were
141: fixed before our 2.1 release, and then a far smaller number needed
142: fixing for our 2.2 release. We do not find as many problems anymore,
143: it is simply a case of diminishing returns. Recently the security
144: problems we find and fix tend to be significantly more obscure or
145: complicated. Still we will persist for a number of reasons:<p>
1.36 deraadt 146:
1.35 deraadt 147: <ul>
1.45 deraadt 148: <li>Occasionally we find a simple problem we missed earlier. Doh!
1.35 deraadt 149: <li>Security is like an arms race; the best attackers will continue
1.45 deraadt 150: to search for more complicated exploits, so we will too.
151: <li>Finding and fixing subtle flaws in complicated software is
152: a lot of fun.
1.35 deraadt 153: </ul>
1.106 deraadt 154: <p>
1.15 deraadt 155:
1.14 deraadt 156: The auditing process is not over yet, and as you can see we continue
1.28 deraadt 157: to find and fix new security flaws.<p>
1.12 deraadt 158:
1.106 deraadt 159: <a name=default></a>
1.110 deraadt 160: <li><h3><font color=#e00000>"Secure by Default"</font></h3><p>
1.106 deraadt 161:
162: To ensure that novice users of OpenBSD do not need to become security
163: experts overnight (a viewpoint which other vendors seem to have), we
164: ship the operating system in a Secure by Default mode. All non-essential
165: services are disabled. As the user/administrator becomes more familiar
166: with the system, he will discover that he has to enable daemons and other
167: parts of the system. During the process of learning how to enable a new
168: service, the novice is more likely to learn of security considerations.<p>
169:
170: This is in stark contrast to the increasing number of systems that
171: ship with NFS, mountd, web servers, and various other services enabled
172: by default, creating instantaneous security problems for their users
173: within minutes after their first install.<p>
174:
1.153 jufi 175: <a name=crypto></a>
1.110 deraadt 176: <li><h3><font color=#e00000>Cryptography</font></h3><p>
1.106 deraadt 177:
178: And of course, since the OpenBSD project is based in Canada, it is possible
179: for us to integrate cryptography. For more information, read the page
1.116 deraadt 180: outlining <a href=crypto.html>what we have done with cryptography</a>.</p>
1.106 deraadt 181:
1.110 deraadt 182: <li><h3><font color=#e00000>Advisories</font></h3><p>
1.106 deraadt 183:
184: <dl>
185:
186: <li>
1.187 ! deraadt 187: <a name=30></a>
! 188:
! 189: <h3><font color=#e00000>OpenBSD 3.0 Security Advisories</font></h3>
! 190: These are the OpenBSD 3.0 advisories -- all these problems are solved
! 191: in <a href=anoncvs.html>OpenBSD current</a> and the
! 192: <a href=stable.html>patch branch</a>.
! 193:
! 194: <p>
! 195: <ul>
! 196: <li>There are no security advisories for 3.0 yet.
! 197: </ul>
! 198:
! 199: <p>
! 200: <li>
1.173 deraadt 201: <a name=29></a>
202:
203: <h3><font color=#e00000>OpenBSD 2.9 Security Advisories</font></h3>
204: These are the OpenBSD 2.9 advisories -- all these problems are solved
205: in <a href=anoncvs.html>OpenBSD current</a> and the
1.179 jufi 206: <a href=stable.html>patch branch</a>.
1.173 deraadt 207:
208: <p>
209: <ul>
1.185 deraadt 210: <li><a href=errata29.html#uucp>September 11, 2001:
1.184 millert 211: A security hole exists in uuxqt(8) that may allow an
212: attacker to gain root privileges.</a>
1.185 deraadt 213: <li><a href=errata29.html#lpd>August 29, 2001:
1.183 millert 214: A security hole exists in lpd(8) that may allow an
215: attacker to gain root privileges if lpd is running.</a>
1.185 deraadt 216: <li><a href=errata29.html#sendmail2>August 21, 2001:
1.181 millert 217: A security hole exists in sendmail(8) that may allow an
218: attacker on the local host to gain root privileges.</a>
1.185 deraadt 219: <li><a href=errata29.html#nfs>July 30, 2001:
1.180 jason 220: A kernel buffer overflow in the NFS code can be used to execute
221: arbitrary code by users with mount privileges (only root by
1.181 millert 222: default).</a>
1.185 deraadt 223: <li><a href=errata29.html#kernexec>June 15, 2001:
1.178 aaron 224: A race condition in the kernel can lead to local root compromise.</a>
1.185 deraadt 225: <li><a href=errata29.html#sshcookie>June 12, 2001:
1.177 markus 226: sshd(8) allows users to delete arbitrary files named "cookies"
227: if X11 forwarding is enabled. X11 forwarding is disabled
228: by default.</a>
1.185 deraadt 229: <li><a href=errata29.html#fts>May 30, 2001:
1.176 millert 230: Programs using the fts routines can be tricked into changing
231: into the wrong directory.</a>
1.185 deraadt 232: <li><a href=errata29.html#sendmail>May 29, 2001:
1.174 millert 233: Sendmail signal handlers contain unsafe code,
234: leading to numerous race conditions.</a>
1.173 deraadt 235: </ul>
236:
237: <p>
238: <li>
1.152 deraadt 239: <a name=28></a>
240:
241: <h3><font color=#e00000>OpenBSD 2.8 Security Advisories</font></h3>
242: These are the OpenBSD 2.8 advisories -- all these problems are solved
1.154 millert 243: in <a href=anoncvs.html>OpenBSD current</a> and the
1.179 jufi 244: <a href=stable.html>patch branch</a>.
1.152 deraadt 245:
246: <p>
247: <ul>
1.184 millert 248: <li><a href=errata28.html#uucp>September 11, 2001:
249: A security hole exists in uuxqt(8) that may allow an
250: attacker to gain root privileges.</a>
1.183 millert 251: <li><a href=errata28.html#lpd>August 29, 2001:
252: A security hole exists in lpd(8) that may allow an
253: attacker to gain root privileges if lpd is running.</a>
1.181 millert 254: <li><a href=errata28.html#sendmail2>August 21, 2001:
255: A security hole exists in sendmail(8) that may allow an
256: attacker on the local host to gain root privileges.</a>
1.178 aaron 257: <li><a href=errata28.html#kernexec>June 15, 2001:
258: A race condition in the kernel can lead to local root compromise.</a>
1.176 millert 259: <li><a href=errata28.html#fts>May 30, 2001:
260: Programs using the fts routines can be tricked into changing
261: into the wrong directory.</a>
1.175 millert 262: <li><a href=errata28.html#sendmail>May 29, 2001:
263: Sendmail signal handlers contain unsafe code,
264: leading to numerous race conditions.</a>
1.173 deraadt 265: <li><a href=errata28.html#ipf_frag>Apr 23, 2001:
1.172 ericj 266: IPF contains a serious bug with its handling of fragment cacheing.</a>
1.173 deraadt 267: <li><a href=errata28.html#glob_limit>Apr 23, 2001:
1.172 ericj 268: ftpd(8) contains a potential DoS relating to glob(3).</a>
1.173 deraadt 269: <li><a href=errata28.html#glob>Apr 10, 2001:
1.170 ericj 270: The glob(3) library call contains multiple buffer overflows.</a>
1.173 deraadt 271: <li><a href=errata28.html#readline>Mar 18, 2001:
1.169 millert 272: The readline library creates history files with permissive modes based on the user's umask.</a>
1.173 deraadt 273: <li><a href=errata28.html#ipsec_ah>Mar 2, 2001:
1.167 ericj 274: Insufficient checks in the IPSEC AH IPv4 option handling code can lead to a buffer overrun in the kernel.</a>
1.173 deraadt 275: <li><a href=errata28.html#userldt>Mar 2, 2001:
1.168 horacio 276: The <b>USER_LDT</b> kernel option allows an attacker to gain access to privileged areas of kernel memory.</a>
1.173 deraadt 277: <li><a href=errata28.html#sudo>Feb 22, 2001:
1.171 millert 278: a non-exploitable buffer overflow was fixed in sudo(8).</a>
1.173 deraadt 279: <li><a href=errata28.html#named>Jan 29, 2001:
1.163 jason 280: merge named(8) with ISC BIND 4.9.8-REL, which fixes some buffer vulnerabilities.</a>
1.173 deraadt 281: <li><a href=errata28.html#rnd>Jan 22, 2001:
1.162 jason 282: rnd(4) did not use all of its input when written to.</a>
1.173 deraadt 283: <li><a href=errata28.html#xlock>Dec 22, 2000:
1.159 ericj 284: xlock(1)'s authentication was re-done to authenticate via a named pipe. (patch and new xlock binaries included).</a>
1.173 deraadt 285: <li><a href=errata28.html#procfs>Dec 18, 2000:
1.157 ericj 286: Procfs contains numerous overflows. Procfs is not used by default in OpenBSD. (patch included).</a>
1.173 deraadt 287: <li><a href=errata28.html#kerberos2>Dec 10, 2000:
1.156 deraadt 288: Another problem exists in KerberosIV libraries (patch included).</a>
1.173 deraadt 289: <li><a href=errata28.html#kerberos>Dec 7, 2000:
1.155 deraadt 290: A set of problems in KerberosIV exist (patch included).</a>
1.173 deraadt 291: <li><a href=errata28.html#ftpd>Dec 4, 2000:
1.154 millert 292: A single-byte buffer overflow exists in ftpd (patch included).</a>
1.152 deraadt 293: </ul>
294:
295: <p>
296: <li>
1.124 deraadt 297: <a name=27></a>
298:
299: <h3><font color=#e00000>OpenBSD 2.7 Security Advisories</font></h3>
300: These are the OpenBSD 2.7 advisories -- all these problems are solved
301: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
302: OpenBSD 2.6 advisories listed below are fixed in OpenBSD 2.7.
303:
304: <p>
305: <ul>
1.169 millert 306: <li><a href=errata27.html#readline>Mar 18, 2001:
307: The readline library creates history files with permissive modes based on the user's umask.</a>
308: <li><a href=errata27.html#sudo>Feb 22, 2001:
309: a buffer overflow was fixed in sudo(8).</a>
1.154 millert 310: <li><a href=errata27.html#ftpd>Dec 4, 2000:
311: A single-byte buffer overflow exists in ftpd (patch included).</a>
1.152 deraadt 312: <li><a href=errata27.html#sshforwarding>Nov 10, 2000:
313: Hostile servers can force OpenSSH clients to do agent or X11 forwarding.
314: (patch included)</a>
315: <li><a href=errata27.html#xtrans>Oct 26, 2000:
1.151 matthieu 316: X11 libraries have 2 potential overflows in xtrans code.
317: (patch included)</a>
1.152 deraadt 318: <li><a href=errata27.html#httpd>Oct 18, 2000:
1.150 beck 319: Apache mod_rewrite and mod_vhost_alias modules could expose files
320: on the server in certain configurations if used.
321: (patch included)</a>
1.164 deraadt 322: <li><a href=errata27.html#telnetd>Oct 10, 2000:
1.149 millert 323: The telnet daemon does not strip out the TERMINFO, TERMINFO_DIRS,
324: TERMPATH and TERMCAP environment variables as it should.
325: (patch included)</a>
1.152 deraadt 326: <li><a href=errata27.html#format_strings>Oct 6, 2000:
1.148 millert 327: There are printf-style format string bugs in several privileged
328: programs. (patch included)</a>
1.152 deraadt 329: <li><a href=errata27.html#curses>Oct 6, 2000:
1.147 millert 330: libcurses honored terminal descriptions in the $HOME/.terminfo
331: directory as well as in the TERMCAP environment variable for
332: setuid and setgid applications.
1.146 deraadt 333: (patch included)</a>
1.152 deraadt 334: <li><a href=errata27.html#talkd>Oct 6, 2000:
1.146 deraadt 335: A format string vulnerability exists in talkd(8).
336: (patch included)</a>
1.152 deraadt 337: <li><a href=errata27.html#pw_error>Oct 3, 2000:
1.145 aaron 338: A format string vulnerability exists in the pw_error() function of the
339: libutil library, yielding localhost root through chpass(1).
340: (patch included)</a>
1.152 deraadt 341: <li><a href=errata27.html#ipsec>Sep 18, 2000:
1.144 jason 342: Bad ESP/AH packets could cause a crash under certain conditions.
343: (patch included)</a>
1.152 deraadt 344: <li><a href=errata27.html#xlock>Aug 16, 2000:
1.141 deraadt 345: A format string vulnerability (localhost root) exists in xlock(1).
346: (patch included)</a>
1.152 deraadt 347: <li><a href=errata27.html#X11_libs>July 14, 2000:
1.139 deraadt 348: Various bugs found in X11 libraries have various side effects, almost
349: completely denial of service in OpenBSD.
350: (patch included)</a>
1.152 deraadt 351: <li><a href=errata27.html#ftpd>July 5, 2000:
1.136 deraadt 352: Just like pretty much all the other unix ftp daemons
353: on the planet, ftpd had a remote root hole in it.
354: Luckily, ftpd was not enabled by default.
1.137 deraadt 355: The problem exists if anonymous ftp is enabled.
1.136 deraadt 356: (patch included)</a>
1.152 deraadt 357: <li><a href=errata27.html#mopd>July 5, 2000:
1.136 deraadt 358: Mopd, very rarely used, contained some buffer overflows.
359: (patch included)</a>
1.152 deraadt 360: <li><a href=errata27.html#libedit>June 28, 2000:
1.135 deraadt 361: libedit would check for a <b>.editrc</b> file in the current
362: directory. Not known to be a real security issue, but a patch
363: is available anyways.
364: (patch included)</a>
1.152 deraadt 365: <li><a href=errata27.html#dhclient>June 24, 2000:
1.134 deraadt 366: A serious bug in dhclient(8) could allow strings from a
367: malicious dhcp server to be executed in the shell as root.
368: (patch included)</a>
1.152 deraadt 369: <li><a href=errata27.html#isakmpd>June 9, 2000:
1.133 deraadt 370: A serious bug in isakmpd(8) policy handling wherein
371: policy verification could be completely bypassed in isakmpd.
372: (patch included)</a>
1.152 deraadt 373: <li><a href=errata27.html#uselogin>June 6, 2000:
1.132 deraadt 374: The non-default flag UseLogin in <b>/etc/sshd_config</b> is broken,
375: should not be used, and results in security problems on
376: other operating systems.</a>
1.152 deraadt 377: <li><a href=errata27.html#bridge>May 26, 2000:
1.129 deraadt 378: The bridge(4) <i>learning</i> flag may be bypassed.
1.128 deraadt 379: (patch included)</a>
1.152 deraadt 380: <li><a href=errata27.html#ipf>May 25, 2000:
1.127 kjell 381: Improper use of ipf <i>keep-state</i> rules can result
382: in firewall rules being bypassed. (patch included)</a>
383:
1.124 deraadt 384: </ul>
385:
386: <p>
387: <li>
1.119 deraadt 388: <a name=26></a>
389:
390: <h3><font color=#e00000>OpenBSD 2.6 Security Advisories</font></h3>
391: These are the OpenBSD 2.6 advisories -- all these problems are solved
392: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
393: OpenBSD 2.5 advisories listed below are fixed in OpenBSD 2.6.
394:
395: <p>
396: <ul>
1.130 deraadt 397: <li><a href=errata26.html#semconfig>May 26, 2000:
398: SYSV semaphore support contained an undocumented system call
1.131 deraadt 399: which could wedge semaphore-using processes from exiting. (patch included)</a>
1.127 kjell 400: <li><a href=errata26.html#ipf>May 25, 2000:
401: Improper use of ipf <i>keep-state</i> rules can result
402: in firewall rules being bypassed. (patch included)</a>
1.126 deraadt 403: <li><a href=errata26.html#xlockmore>May 25, 2000:
1.125 deraadt 404: xlockmore has a bug which a localhost attacker can use to gain
405: access to the encrypted root password hash (which is normally
406: encoded using blowfish (see
407: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=crypt&sektion=3">
408: crypt(3)</a>)
409: (patch included).</a>
1.126 deraadt 410: <li><a href=errata26.html#procfs>Jan 20, 2000:
1.123 deraadt 411: Systems running with procfs enabled and mounted are
412: vulnerable to a very tricky exploit. procfs is not
413: mounted by default.
414: (patch included).</a>
1.126 deraadt 415: <li><a href=errata26.html#ifmedia>Nov 9, 1999:
1.125 deraadt 416: Any user could change interface media configurations, resulting in
417: a localhost denial of service attack.
1.119 deraadt 418: (patch included).</a>
1.126 deraadt 419: <li><a href=errata26.html#sslUSA>Dec 2, 1999:
1.120 deraadt 420: A buffer overflow in the RSAREF code included in the
421: USA version of libssl, is possibly exploitable in
422: httpd, ssh, or isakmpd, if SSL/RSA features are enabled.
1.124 deraadt 423: (patch included).<br></a>
424: <strong>Update:</strong> Turns out that this was not exploitable
425: in any of the software included in OpenBSD 2.6.
1.126 deraadt 426: <li><a href=errata26.html#sendmail>Dec 4, 1999:
1.121 deraadt 427: Sendmail permitted any user to cause a aliases file wrap,
428: thus exposing the system to a race where the aliases file
429: did not exist.
430: (patch included).</a>
1.119 deraadt 431: </ul>
432:
433: <p>
434: <li>
435:
1.93 deraadt 436: <a name=25></a>
1.106 deraadt 437:
1.110 deraadt 438: <h3><font color=#e00000>OpenBSD 2.5 Security Advisories</font></h3>
1.93 deraadt 439: These are the OpenBSD 2.5 advisories -- all these problems are solved
440: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
441: OpenBSD 2.4 advisories listed below are fixed in OpenBSD 2.5.
442:
1.96 deraadt 443: <p>
1.104 deraadt 444: <ul>
1.117 deraadt 445: <li><a href=errata25.html#cron>Aug 30, 1999:
1.103 deraadt 446: In cron(8), make sure argv[] is NULL terminated in the
447: fake popen() and run sendmail as the user, not as root.
448: (patch included).</a>
1.117 deraadt 449: <li><a href=errata25.html#miscfs>Aug 12, 1999: The procfs and fdescfs
1.101 deraadt 450: filesystems had an overrun in their handling of uio_offset
451: in their readdir() routines. (These filesystems are not
452: enabled by default). (patch included).</a>
1.117 deraadt 453: <li><a href=errata25.html#profil>Aug 9, 1999: Stop profiling (see profil(2))
1.100 deraadt 454: when we execve() a new process. (patch included).</a>
1.117 deraadt 455: <li><a href=errata25.html#ipsec_in_use>Aug 6, 1999: Packets that should have
1.98 deraadt 456: been handled by IPsec may be transmitted as cleartext.
457: PF_KEY SA expirations may leak kernel resources.
458: (patch included).</a>
1.117 deraadt 459: <li><a href=errata25.html#rc>Aug 5, 1999: In /etc/rc, use mktemp(1) for
1.97 deraadt 460: motd re-writing and change the find(1) to use -execdir
461: (patch included).</a>
1.117 deraadt 462: <li><a href=errata25.html#chflags>Jul 30, 1999: Do not permit regular
1.95 deraadt 463: users to chflags(2) or fchflags(2) on character or block devices
464: which they may currently be the owner of (patch included).</a>
1.117 deraadt 465: <li><a href=errata25.html#nroff>Jul 27, 1999: Cause groff(1) to be invoked
1.95 deraadt 466: with the -S flag, when called by nroff(1) (patch included).</a>
1.93 deraadt 467: </ul>
468:
1.106 deraadt 469: <p>
470: <li>
1.75 deraadt 471: <a name=24></a>
1.110 deraadt 472: <h3><font color=#e00000>OpenBSD 2.4 Security Advisories</font></h3>
1.75 deraadt 473: These are the OpenBSD 2.4 advisories -- all these problems are solved
474: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
475: OpenBSD 2.3 advisories listed below are fixed in OpenBSD 2.4.
476:
1.96 deraadt 477: <p>
1.75 deraadt 478: <ul>
1.92 deraadt 479: <li><a href=errata24.html#poll>Mar 22, 1999: The nfds argument for poll(2) needs
1.91 deraadt 480: to be constrained, to avoid kvm starvation (patch included).</a>
1.92 deraadt 481: <li><a href=errata24.html#tss>Mar 21, 1999: A change in TSS handling stops
1.91 deraadt 482: another kernel crash case caused by the <strong>crashme</strong>
483: program (patch included).</a>
1.92 deraadt 484: <li><a href=errata24.html#nlink>Feb 25, 1999: An unbounded increment on the
1.90 deraadt 485: nlink value in FFS and EXT2FS filesystems can cause a system crash.
1.89 deraadt 486: (patch included).</a>
1.92 deraadt 487: <li><a href=errata24.html#ping>Feb 23, 1999: Yet another buffer overflow
1.88 deraadt 488: existed in ping(8). (patch included).</a>
1.92 deraadt 489: <li><a href=errata24.html#ipqrace>Feb 19, 1999: ipintr() had a race in use of
1.87 deraadt 490: the ipq, which could permit an attacker to cause a crash.
491: (patch included).</a>
1.92 deraadt 492: <li><a href=errata24.html#accept>Feb 17, 1999: A race condition in the
1.86 deraadt 493: kernel between accept(2) and select(2) could permit an attacker
494: to hang sockets from remote.
495: (patch included).</a>
1.92 deraadt 496: <li><a href=errata24.html#maxqueue>Feb 17, 1999: IP fragment assembly can
1.85 deraadt 497: bog the machine excessively and cause problems.
498: (patch included).</a>
1.92 deraadt 499: <li><a href=errata24.html#trctrap>Feb 12, 1999: i386 T_TRCTRAP handling and
1.84 deraadt 500: DDB interacted to possibly cause a crash.
501: (patch included).</a>
1.92 deraadt 502: <li><a href=errata24.html#rst>Feb 11, 1999: TCP/IP RST handling was sloppy.
1.83 deraadt 503: (patch included).</a>
1.92 deraadt 504: <li><a href=errata24.html#bootpd>Nov 27, 1998: There is a remotely exploitable
1.81 deraadt 505: problem in bootpd(8). (patch included).</a>
1.92 deraadt 506: <li><a href=errata24.html#termcap>Nov 19, 1998: There is a possibly locally
1.82 deraadt 507: exploitable problem relating to environment variables in termcap
508: and curses. (patch included).</a>
1.92 deraadt 509: <li><a href=errata24.html#tcpfix>Nov 13, 1998: There is a remote machine lockup
1.78 deraadt 510: bug in the TCP decoding kernel. (patch included).</a>
1.75 deraadt 511: </ul>
512:
1.106 deraadt 513: <p>
514: <li>
1.58 deraadt 515: <a name=23></a>
1.110 deraadt 516: <h3><font color=#e00000>OpenBSD 2.3 Security Advisories</font></h3>
1.73 deraadt 517: These are the OpenBSD 2.3 advisories -- all these problems are solved
518: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
519: OpenBSD 2.2 advisories listed below are fixed in OpenBSD 2.3.
1.53 matthieu 520:
1.96 deraadt 521: <p>
1.53 matthieu 522: <ul>
1.81 deraadt 523: <li><a href=errata23.html#bootpd>Nov 27, 1998: There is a remotely exploitable
524: problem in bootpd(8). (patch included).</a>
1.78 deraadt 525: <li><a href=errata23.html#tcpfix>Nov 13, 1998: There is a remote machine lockup
526: bug in the TCP decoding kernel. (patch included).</a>
1.76 aaron 527: <li><a href=errata23.html#fdalloc>Jul 2, 1998: setuid and setgid processes
1.72 deraadt 528: should not be executed with fd slots 0, 1, or 2 free.
529: (patch included).</a>
1.79 deraadt 530: <li><a href=errata23.html#resolver>August 31, 1998: A benign looking resolver buffer overflow bug was re-introduced accidentally (patches included).</a>
1.76 aaron 531: <li><a href=errata23.html#xlib>June 6, 1998: Further problems with the X
1.71 deraadt 532: libraries (patches included).</a>
1.76 aaron 533: <li><a href=errata23.html#pctr>June 4, 1998: on non-Intel i386 machines, any user
1.72 deraadt 534: can use pctr(4) to crash the machine.</a>
1.76 aaron 535: <li><a href=errata23.html#kill>May 17, 1998: kill(2) of setuid/setgid target
1.66 deraadt 536: processes too permissive (4th revision patch included).</a>
1.76 aaron 537: <li><a href=errata23.html#immutable>May 11, 1998: mmap() permits partial bypassing
1.60 deraadt 538: of immutable and append-only file flags. (patch included).</a>
1.76 aaron 539: <li><a href=errata23.html#xterm-xaw>May 1, 1998: Buffer overflow in xterm and Xaw
1.58 deraadt 540: (CERT advisory VB-98.04) (patch included).</a>
1.76 aaron 541: <li><a href=errata23.html#ipsec>May 5, 1998: Incorrect handling of IPSEC packets
1.59 deraadt 542: if IPSEC is enabled (patch included).</a>
1.53 matthieu 543: </ul>
1.9 deraadt 544:
1.106 deraadt 545: <p>
546: <li>
1.58 deraadt 547: <a name=22></a>
1.110 deraadt 548: <h3><font color=#e00000>OpenBSD 2.2 Security Advisories</font></h3>
1.45 deraadt 549: These are the OpenBSD 2.2 advisories. All these problems are solved
1.55 deraadt 550: in <a href=23.html>OpenBSD 2.3</a>. Some of these problems
1.45 deraadt 551: still exist in other operating systems. (The supplied patches are for
552: OpenBSD 2.2; they may or may not work on OpenBSD 2.1).
1.9 deraadt 553:
1.96 deraadt 554: <p>
1.9 deraadt 555: <ul>
1.72 deraadt 556: <li><a href=errata22.html#ipsec>May 5, 1998: Incorrect handling of IPSEC
557: packets if IPSEC is enabled (patch included).</a>
558: <li><a href=errata22.html#xterm-xaw>May 1, 1998: Buffer overflow in xterm
559: and Xaw (CERT advisory VB-98.04) (patch included).</a>
560: <li><a href=errata22.html#uucpd>Apr 22, 1998: Buffer overflow in uucpd
561: (patch included).</a>
562: <li><a href=errata22.html#rmjob>Apr 22, 1998: Buffer mismanagement in lprm
563: (patch included).</a>
564: <li><a href=errata22.html#ping>Mar 31, 1998: Overflow in ping -R (patch included).</a>
565: <li><a href=errata22.html#named>Mar 30, 1998: Overflow in named fake-iquery
1.59 deraadt 566: (patch included).</a>
1.72 deraadt 567: <li><a href=errata22.html#mountd>Mar 2, 1998: Accidental NFS filesystem
568: export (patch included).</a>
1.112 philen 569: <li><a href="advisories/mmap.txt">Feb 26, 1998: Read-write mmap() flaw.</a>
1.72 deraadt 570: Revision 3 of the patch is available <a href=errata22.html#mmap>here</a>
1.112 philen 571: <li><a href="advisories/sourceroute.txt">Feb 19, 1998: Sourcerouted Packet
1.59 deraadt 572: Acceptance.</a>
1.50 deraadt 573: A patch is available <a href=errata22.html#sourceroute>here</a>.
1.122 rohee 574: <li><a href=errata22.html#ruserok>Feb 13, 1998: Setuid coredump & Ruserok()
1.72 deraadt 575: flaw (patch included).</a>
576: <li><a href=errata22.html#ldso>Feb 9, 1998: MIPS ld.so flaw (patch included).</a>
577: <li><a href=errata22.html#f00f>Dec 10, 1997: Intel P5 f00f lockup
1.59 deraadt 578: (patch included).</a>
1.1 deraadt 579: </ul>
580:
1.106 deraadt 581: <p>
582: <li>
1.58 deraadt 583: <a name=21></a>
1.110 deraadt 584: <h3><font color=#e00000>OpenBSD 2.1 Security Advisories</font></h3>
1.52 deraadt 585: These are the OpenBSD 2.1 advisories. All these problems are solved
586: in <a href=22.html>OpenBSD 2.2</a>. Some of these problems still
587: exist in other operating systems. (If you are running OpenBSD 2.1, we
588: would strongly recommend an upgrade to the newest release, as this
589: patch list only attempts at fixing the most important security
590: problems. In particular, OpenBSD 2.2 fixes numerous localhost
591: security problems. Many of those problems were solved in ways which
592: make it hard for us to provide patches).
593:
1.96 deraadt 594: <p>
1.52 deraadt 595: <ul>
1.112 philen 596: <li><a href="advisories/signals.txt">Sep 15, 1997: Deviant Signals (patch included)</a>
597: <li><a href="advisories/rfork.txt">Aug 2, 1997: Rfork() system call flaw
1.59 deraadt 598: (patch included)</a>
1.112 philen 599: <li><a href="advisories/procfs.txt">Jun 24, 1997: Procfs flaws (patch included)</a>
1.52 deraadt 600: </ul>
1.51 deraadt 601:
1.106 deraadt 602: <p>
603: <li>
604: <a name=20></a>
1.110 deraadt 605: <h3><font color=#e00000>OpenBSD 2.0 Security Advisories</font></h3>
1.99 deraadt 606: These are the OpenBSD 2.0 advisories. All these problems are solved
607: in <a href=21.html>OpenBSD 2.1</a>. Some of these problems still
608: exist in other operating systems. (If you are running OpenBSD 2.0, we
609: commend you for being there back in the old days!, but you're really
610: missing out if you don't install a new version!)
611:
612: <p>
613: <ul>
1.112 philen 614: <li><a href="advisories/res_random.txt">April 22, 1997: Predictable IDs in the
1.99 deraadt 615: resolver (patch included)</a>
616: <li>Many others... if people can hunt them down, please let me know
617: and we'll put them up here.
618: </ul>
619:
1.106 deraadt 620: </dl>
1.51 deraadt 621: <p>
1.106 deraadt 622:
623: <a name=watching></a>
1.110 deraadt 624: <li><h3><font color=#e00000>Watching our Changes</font></h3><p>
1.106 deraadt 625:
1.21 deraadt 626: Since we take a proactive stance with security, we are continually
627: finding and fixing new security problems. Not all of these problems
1.80 espie 628: get widely reported because (as stated earlier) many of them are not
1.45 deraadt 629: confirmed to be exploitable; many simple bugs we fix do turn out to
630: have security consequences we could not predict. We do not have the
631: time resources to make these changes available in the above format.<p>
1.21 deraadt 632:
633: Thus there are usually minor security fixes in the current source code
634: beyond the previous major OpenBSD release. We make a limited
1.45 deraadt 635: guarantee that these problems are of minimal impact and unproven
1.44 ian 636: exploitability. If we discover that a problem definitely matters for
1.45 deraadt 637: security, patches will show up here <strong>VERY</strong> quickly.<p>
1.21 deraadt 638:
1.45 deraadt 639: People who are really concerned with security can do a number of
640: things:<p>
1.21 deraadt 641:
642: <ul>
643: <li>If you understand security issues, watch our
1.27 deraadt 644: <a href=mail.html>source-changes mailing list</a> and keep an
1.23 deraadt 645: eye out for things which appear security related. Since
1.21 deraadt 646: exploitability is not proven for many of the fixes we make,
647: do not expect the relevant commit message to say "SECURITY FIX!".
648: If a problem is proven and serious, a patch will be available
649: here very shortly after.
1.161 horacio 650: <li>In addition to source changes, you can watch our <a href="mail.html">
1.160 ericj 651: security-announce mailing list</a> which will notify you for every
1.186 ian 652: security related item that the OpenBSD team deems as a possible threat,
1.160 ericj 653: and instruct you on how to patch the problem.
1.21 deraadt 654: <li>Track our current source code tree, and teach yourself how to do a
1.29 deraadt 655: complete system build from time to time (read /usr/src/Makefile
656: carefully). Users can make the assumption that the current
657: source tree always has stronger security than the previous release.
1.45 deraadt 658: However, building your own system from source code is not trivial;
659: it is nearly 300MB of source code, and problems do occur as we
660: transition between major releases.
1.115 ericj 661: <li>Install a binary snapshot for your
1.80 espie 662: architecture, which are made available fairly often. For
1.29 deraadt 663: instance, an i386 snapshot is typically made available weekly.
1.21 deraadt 664: </ul>
665:
1.9 deraadt 666: <p>
1.153 jufi 667: <a name=reporting></a>
1.110 deraadt 668: <li><h3><font color=#e00000>Reporting problems</font></h3><p>
1.3 deraadt 669:
1.5 deraadt 670: <p> If you find a new security problem, you can mail it to
1.6 deraadt 671: <a href=mailto:deraadt@openbsd.org>deraadt@openbsd.org</a>.
1.7 deraadt 672: <br>
1.5 deraadt 673: If you wish to PGP encode it (but please only do so if privacy is very
1.112 philen 674: urgent, since it is inconvenient) use this <a href="advisories/pgpkey.txt">pgp key</a>.
1.5 deraadt 675:
1.107 deraadt 676: <p>
677: <a name=papers></a>
1.110 deraadt 678: <li><h3><font color=#e00000>Further Reading</font></h3><p>
1.107 deraadt 679:
680: A number of papers have been written by OpenBSD team members, about security
681: related changes they have done in OpenBSD. The postscript versions of these
1.108 deraadt 682: documents are available as follows.<p>
1.107 deraadt 683:
684: <ul>
1.113 deraadt 685: <li>A Future-Adaptable Password Scheme.<br>
1.118 deraadt 686: <a href=events.html#usenix99>Usenix 1999</a>,
1.153 jufi 687: by <a href=mailto:provos@openbsd.org>Niels Provos</a>,
1.113 deraadt 688: <a href=mailto:dm@openbsd.org>David Mazieres</a>.<br>
1.107 deraadt 689: <a href=papers/bcrypt-paper.ps>paper</a> and
690: <a href=papers/bcrypt-slides.ps>slides</a>.
1.113 deraadt 691: <p>
692: <li>Cryptography in OpenBSD: An Overview.<br>
1.118 deraadt 693: <a href=events.html#usenix99>Usenix 1999</a>,
1.113 deraadt 694: by <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>,
695: <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>,
696: <a href=mailto:art@openbsd.org>Artur Grabowski</a>,
697: <a href=mailto:angelos@openbsd.org>Angelos D. Keromytis</a>,
698: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.107 deraadt 699: <a href=papers/crypt-paper.ps>paper</a> and
700: <a href=papers/crypt-slides.ps>slides</a>.
1.113 deraadt 701: <p>
702: <li>strlcpy and strlcat -- consistent, safe, string copy and concatenation.<br>
1.118 deraadt 703: <a href=events.html#usenix99>Usenix 1999</a>,
1.113 deraadt 704: by <a href=mailto:millert@openbsd.org>Todd C. Miller</a>,
705: <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>.<br>
1.109 deraadt 706: <a href=papers/strlcpy-paper.ps>paper</a> and
707: <a href=papers/strlcpy-slides.ps>slides</a>.
1.113 deraadt 708: <p>
1.118 deraadt 709: <li>Dealing with Public Ethernet Jacks-Switches, Gateways, and Authentication.<br>
710: <a href=events.html#lisa99>LISA 1999</a>,
711: by <a href=mailto:beck@openbsd.org>Bob Beck</a>.<br>
712: <a href=papers/authgw-paper.ps>paper</a> and
713: <a href=papers/authgw-slides.ps>slides</a>.
714: <p>
1.153 jufi 715: <li>Encrypting Virtual Memory<br>
1.142 deraadt 716: <a href=events.html#sec2000>Usenix Security 2000</a>,
717: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.143 provos 718: <a href=papers/swapencrypt.ps>paper</a> and
719: <a href=papers/swapencrypt-slides.ps>slides</a>.
1.142 deraadt 720: <p>
1.107 deraadt 721: </ul>
722:
1.106 deraadt 723: </dl>
724:
1.2 deraadt 725: <hr>
1.68 pauls 726: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.24 deraadt 727: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
728: <br>
1.187 ! deraadt 729: <small>$OpenBSD: security.html,v 1.186 2001/10/23 11:37:26 ian Exp $</small>
1.1 deraadt 730:
1.24 deraadt 731: </body>
732: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to security.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www