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