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