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