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