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