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