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