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