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