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