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