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