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