[BACK]Return to security.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/security.html, Revision 1.258

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