<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version="0.92">
  <channel>
    <title>OpenBSD 43 Errata</title>
    <link>http://www.openbsd.org/errata43.html</link>
    <description>OpenBSD 43 Errata</description>
    <language>en-us</language>
    <managingEditor>mike@erdelynet.com</managingEditor>

    <image>
      <title>erdelynet.com</title>
      <url>http://erdelynet.com/images/puffy96x83.gif</url>
      <link>http://www.openbsd.org/errata43.html</link>
      <width>96</width>
      <height>83</height>
      <description>OpenBSD 43 Errata</description>
    </image>

    <item>
      <title>013 RELIABILITY 013_pf</title>
      <link>http://www.openbsd.org/errata43.html#013_pf</link>
      <category>RELIABILITY</category>
      <architecture>All architectures</architecture>
      <pubDate>April 11, 2009</pubDate>
      <description><![CDATA[
 When pf attempts to perform translation on a specially crafted IP datagram, a null pointer dereference will occur, resulting in a kernel panic. In certain configurations this may be triggered by a remote attacker. <br> Restricting translation rules to protocols that are specific to the IP version in use, is an effective workaround until the patch can be installed. As an example, for IPv4 nat/binat/rdr rules you can use: <pre>     nat/rdr ... inet proto { tcp udp icmp } ... </pre> Or for IPv6 nat/binat/rdr rules you can use: <pre>     nat/rdr ... inet6 proto { tcp udp icmp6 } ... </pre> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/013_pf.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>012 RELIABILITY 012_openssl</title>
      <link>http://www.openbsd.org/errata43.html#012_openssl</link>
      <category>RELIABILITY</category>
      <architecture>All architectures</architecture>
      <pubDate>April 8, 2009</pubDate>
      <description><![CDATA[
 The OpenSSL ASN.1 handling code could be forced to perform invalid memory accesses through the use of certain invalid strings (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>) or under certain error conditions triggerable by invalid ASN.1 structures (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0789">CVE-2009-0789</a>). These vulnerabilities could be exploited to achieve a denial-of-service. A more detailed description of these problems is available in the <a href="http://www.openssl.org/news/secadv_20090325.txt">OpenSSL security advisory</a>, but note that the other issue described there "Incorrect Error Checking During CMS verification" relates to code not enabled in OpenBSD. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/012_openssl.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>011 SECURITY 011_sudo</title>
      <link>http://www.openbsd.org/errata43.html#011_sudo</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>February 22, 2009</pubDate>
      <description><![CDATA[
 sudo(8) may allow a user listed in the sudoers file to run a command as a different user than their access rule specifies when a Unix group is used in the RunAs portion of the rule.  The bug only manifests when the user being granted privileges is also a member of the group in the RunAs portion of the rule. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/011_sudo.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>010 RELIABILITY 010_bgpd</title>
      <link>http://www.openbsd.org/errata43.html#010_bgpd</link>
      <category>RELIABILITY</category>
      <architecture>All architectures</architecture>
      <pubDate>February 18, 2009</pubDate>
      <description><![CDATA[
 bgpd(8) did not correctly prepend its own AS to very long AS paths, causing the process to terminate because of the resulting corrupt path. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/010_bgpd.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>009 RELIABILITY 009_bgpd</title>
      <link>http://www.openbsd.org/errata43.html#009_bgpd</link>
      <category>RELIABILITY</category>
      <architecture>All architectures</architecture>
      <pubDate>January 30, 2009</pubDate>
      <description><![CDATA[
 Upon reception of an invalid update with 4-byte AS attributes, bgpd - adhering to the RFCs - closed the session to the neighbor. This error in the specification allowed 3rd parties to close remote BGP sessions. In the worst case Internet connectivity could be lost. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/009_bgpd.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>008 SECURITY 008_bind</title>
      <link>http://www.openbsd.org/errata43.html#008_bind</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>January 14, 2009</pubDate>
      <description><![CDATA[
 named(8) did not correctly check the return value of a DSA verification function, potentially allowing bypass of verification of DNSSEC DSA signatures. <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0025">CVE-2009-0025</a>. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/008_bind.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>007 SECURITY 007_openssl</title>
      <link>http://www.openbsd.org/errata43.html#007_openssl</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>January 9, 2009</pubDate>
      <description><![CDATA[
 The OpenSSL libraries did not correctly check the return value from certain verification functions, allowing validation to be bypassed and permitting a remote attacker to conduct a "man in the middle attack" against SSL/TLS connections if the server is configured with a DSA or ECDSA certificate. <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5077">CVE-2008-5077</a>. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/007_openssl.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>006 SECURITY 006_ndp</title>
      <link>http://www.openbsd.org/errata43.html#006_ndp</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>October 2, 2008</pubDate>
      <description><![CDATA[
 The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor solicitation requests maybe allowing a nearby attacker to intercept traffic. The attacker must have IPv6 connectivity to the same router as their target for this vulnerability to be exploited. <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2476">CVE-2008-2476</a>. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/006_ndp.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>005 RELIABILITY 005_pcb</title>
      <link>http://www.openbsd.org/errata43.html#005_pcb</link>
      <category>RELIABILITY</category>
      <architecture>All architectures</architecture>
      <pubDate>July 29, 2008</pubDate>
      <description><![CDATA[
 Some kinds of IPv6 usage would leak kernel memory (in particular, this path  was exercised by the named(8) patch for port randomization).  Since INET6 is  enabled by default, this condition affects all systems. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/005_pcb.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>004 SECURITY 004_bind</title>
      <link>http://www.openbsd.org/errata43.html#004_bind</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>July 23, 2008</pubDate>
      <description><![CDATA[
 <strong>2nd revision, July 23, 2008</strong><br> A vulnerability has been found with BIND. An attacker could use this vulnerability to poison the cache of a recursive resolving name server. <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447">CVE-2008-1447</a>. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/004_bind.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>003 SECURITY 003_xorg</title>
      <link>http://www.openbsd.org/errata43.html#003_xorg</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>July 15, 2008</pubDate>
      <description><![CDATA[
 Multiple vulnerabilities have been discovered in X.Org.<br> RENDER Extension heap buffer overflow, RENDER Extension crash, RENDER Extension memory corruption, MIT-SHM arbitrary memory read, RECORD and Security extensions memory corruption. <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2360">CVE-2008-2360</a>, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2361">CVE-2008-2361</a>, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2362">CVE-2008-2362</a>, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1379">CVE-2008-1379</a>, <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1377">CVE-2008-1377</a>. <br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/003_xorg.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>002 SECURITY 002_openssh2</title>
      <link>http://www.openbsd.org/errata43.html#002_openssh2</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>April 3, 2008</pubDate>
      <description><![CDATA[
 Avoid possible hijacking of X11-forwarded connections with sshd(8) by refusing to listen on a port unless all address families bind successfully.<br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/002_openssh2.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

    <item>
      <title>001 SECURITY 001_openssh</title>
      <link>http://www.openbsd.org/errata43.html#001_openssh</link>
      <category>SECURITY</category>
      <architecture>All architectures</architecture>
      <pubDate>March 30, 2008</pubDate>
      <description><![CDATA[
 sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em> directive was in effect, allowing users with write access to this file to execute arbitrary commands. This behaviour was documented, but was an unsafe default and an extra hassle for administrators.<br> <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.3/common/001_openssh.patch"> A source code patch exists which remedies this problem</a>.<br>
]]></description>
    </item>

  </channel>
</rss>
