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