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