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

Annotation of www/security.html, Revision 1.291

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