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