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