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