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