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