===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata45.html,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- www/errata45.html	2019/05/27 22:55:20	1.62
+++ www/errata45.html	2019/05/28 16:32:42	1.63
@@ -86,92 +86,110 @@
 <hr>
 
 <ul>
-<li id="p016_openssl">
-<strong>016: SECURITY FIX: April 14, 2010</strong>
-&nbsp; <i>All architectures</i><br>
-In TLS connections, certain incorrectly formatted records can cause
-an OpenSSL client or server to crash due to a read attempt at NULL.
-<br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/016_openssl.patch">
-A source code patch exists which remedies this problem.</a>
-<p>
 
-<li id="p015_mpi">
-<strong>015: RELIABILITY FIX: April 4, 2010</strong>
+<li id="p001_openssl">
+<strong>001: RELIABILITY FIX: April 8, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-When updating sensors showing the state of RAID volumes
-<a href="https://man.openbsd.org/OpenBSD-4.5/mpi.4">mpi(4)</a>
-allocates temporary memory and then returns it to the kernel as
-device memory.
-This causes kernel memory usage to be misrepresented, eventually
-leading to a denial of service when a resource limit is apparently
-reached.
+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="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/015_mpi.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/001_openssl.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p014_kerberos">
-<strong>014: RELIABILITY FIX: March 31, 2010</strong>
+<li id="p002_pf">
+<strong>002: RELIABILITY FIX: April 11, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-When decrypting packets, the internal decryption functions were not
-paranoid enough in checking for underruns, which could potentially
-lead to crashes.
+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>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/014_kerberos.patch">
+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="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/002_pf.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p013_ftpd">
-<strong>013: RELIABILITY FIX: March 12, 2010</strong>
-&nbsp; <i>All architectures</i><br>
-Due to a null pointer dereference, it would be possible to crash ftpd when
-handling glob(3)'ing requests. This is non-exploitable.
+<li id="p003_bus_dma">
+<strong>003: RELIABILITY FIX: April 24, 2009</strong>
+&nbsp; <i>i386 only</i><br>
+When DMA'able memory is mapped by device drivers, the
+mapping flags and protection are partially uninitialized.
+Depending on the calling context, this may cause devices to misbehave, like
+<a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
+to stutter, but other anomalies might be observed for other
+device types.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/013_ftpd.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/003_bus_dma.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p012_openssl">
-<strong>012: SECURITY FIX: March 12, 2010</strong>
+<li id="p004_aucat">
+<strong>004: RELIABILITY FIX: April 24, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-OpenSSL is susceptible to a buffer overflow due to a failure
-to check for NULL returns from bn_wexpand function calls.
+In server mode when in full-duplex mode (the default)
+<a href="https://man.openbsd.org/OpenBSD-4.5/aucat.1">aucat(1)</a>
+will send each synchronization message twice, causing client applications
+to think that buffer underruns are occuring.  Depending on the
+application, this may cause the sound to stutter.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/012_openssl.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/004_aucat.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p011_ptrace">
-<strong>011: RELIABILITY FIX: January 29, 2010</strong>
+<li id="p005_audio">
+<strong>005: RELIABILITY FIX: April 24, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-By using ptrace(2) on an ancestor process, a loop in the process tree
-could be created, violating assumptions in other parts of the kernel
-and resulting in infinite loops.
+On very high system load, an audio interrupt may occur while the
+audio process is filling audio ring buffers. This triggers bogus
+(and useless) correction code in the
+<a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
+driver causing the audio application to go out of sync, and in turn causing
+continuous stuttering until the application is restarted.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/011_ptrace.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/005_audio.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p010_openssl">
-<strong>010: SECURITY FIX: November 26, 2009</strong>
+<li id="p006_perl">
+<strong>006: RELIABILITY FIX: June 24, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-The SSL/TLS protocol is subject to man-in-the-middle attacks related to
-renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
-OpenSSL permitted this protocol feature by default and had no way to
-disable it.
+An off-by-one error in the inflate function in Zlib.xs in the
+Compress::Raw::Zlib perl module before 2.017 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1391">CVE-2009-1391</a>),
+as used in AMaViS, SpamAssassin, and possibly other products,
+allows context-dependent attackers to cause a denial of service
+(hang or crash) via a crafted zlib compressed stream that
+triggers a heap-based buffer overflow.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/010_openssl.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/006_perl_zlib.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p009_getsockopt">
-<strong>009: RELIABILITY FIX: October 28, 2009</strong>
+<li id="p007_bind">
+<strong>007: RELIABILITY FIX: July 29, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
-IP_IPCOMP_LEVEL will crash the system.
+A vulnerability has been found in BIND's named server
+(<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
+An attacker could crash a server with a specially crafted dynamic update message to a
+zone for which the server is master.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/009_getsockopt.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/007_bind.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
@@ -184,110 +202,92 @@
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p007_bind">
-<strong>007: RELIABILITY FIX: July 29, 2009</strong>
+<li id="p009_getsockopt">
+<strong>009: RELIABILITY FIX: October 28, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-A vulnerability has been found in BIND's named server
-(<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
-An attacker could crash a server with a specially crafted dynamic update message to a
-zone for which the server is master.
+getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
+IP_IPCOMP_LEVEL will crash the system.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/007_bind.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/009_getsockopt.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p006_perl">
-<strong>006: RELIABILITY FIX: June 24, 2009</strong>
+<li id="p010_openssl">
+<strong>010: SECURITY FIX: November 26, 2009</strong>
 &nbsp; <i>All architectures</i><br>
-An off-by-one error in the inflate function in Zlib.xs in the
-Compress::Raw::Zlib perl module before 2.017 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1391">CVE-2009-1391</a>),
-as used in AMaViS, SpamAssassin, and possibly other products,
-allows context-dependent attackers to cause a denial of service
-(hang or crash) via a crafted zlib compressed stream that
-triggers a heap-based buffer overflow.
+The SSL/TLS protocol is subject to man-in-the-middle attacks related to
+renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
+OpenSSL permitted this protocol feature by default and had no way to
+disable it.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/006_perl_zlib.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/010_openssl.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
+<li id="p011_ptrace">
+<strong>011: RELIABILITY FIX: January 29, 2010</strong>
+&nbsp; <i>All architectures</i><br>
+By using ptrace(2) on an ancestor process, a loop in the process tree
+could be created, violating assumptions in other parts of the kernel
+and resulting in infinite loops.
+<br>
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/011_ptrace.patch">
+A source code patch exists which remedies this problem.</a>
+<p>
 
-<li id="p005_audio">
-<strong>005: RELIABILITY FIX: April 24, 2009</strong>
+<li id="p012_openssl">
+<strong>012: SECURITY FIX: March 12, 2010</strong>
 &nbsp; <i>All architectures</i><br>
-On very high system load, an audio interrupt may occur while the
-audio process is filling audio ring buffers. This triggers bogus
-(and useless) correction code in the
-<a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
-driver causing the audio application to go out of sync, and in turn causing
-continuous stuttering until the application is restarted.
+OpenSSL is susceptible to a buffer overflow due to a failure
+to check for NULL returns from bn_wexpand function calls.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/005_audio.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/012_openssl.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p004_aucat">
-<strong>004: RELIABILITY FIX: April 24, 2009</strong>
+<li id="p013_ftpd">
+<strong>013: RELIABILITY FIX: March 12, 2010</strong>
 &nbsp; <i>All architectures</i><br>
-In server mode when in full-duplex mode (the default)
-<a href="https://man.openbsd.org/OpenBSD-4.5/aucat.1">aucat(1)</a>
-will send each synchronization message twice, causing client applications
-to think that buffer underruns are occuring.  Depending on the
-application, this may cause the sound to stutter.
+Due to a null pointer dereference, it would be possible to crash ftpd when
+handling glob(3)'ing requests. This is non-exploitable.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/004_aucat.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/013_ftpd.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p003_bus_dma">
-<strong>003: RELIABILITY FIX: April 24, 2009</strong>
-&nbsp; <i>i386 only</i><br>
-When DMA'able memory is mapped by device drivers, the
-mapping flags and protection are partially uninitialized.
-Depending on the calling context, this may cause devices to misbehave, like
-<a href="https://man.openbsd.org/OpenBSD-4.5/audio.4">audio(4)</a>
-to stutter, but other anomalies might be observed for other
-device types.
+<li id="p014_kerberos">
+<strong>014: RELIABILITY FIX: March 31, 2010</strong>
+&nbsp; <i>All architectures</i><br>
+When decrypting packets, the internal decryption functions were not
+paranoid enough in checking for underruns, which could potentially
+lead to crashes.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/003_bus_dma.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/014_kerberos.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p002_pf">
-<strong>002: RELIABILITY FIX: April 11, 2009</strong>
+<li id="p015_mpi">
+<strong>015: RELIABILITY FIX: April 4, 2010</strong>
 &nbsp; <i>All architectures</i><br>
-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.
+When updating sensors showing the state of RAID volumes
+<a href="https://man.openbsd.org/OpenBSD-4.5/mpi.4">mpi(4)</a>
+allocates temporary memory and then returns it to the kernel as
+device memory.
+This causes kernel memory usage to be misrepresented, eventually
+leading to a denial of service when a resource limit is apparently
+reached.
 <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="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/002_pf.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/015_mpi.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 
-<li id="p001_openssl">
-<strong>001: RELIABILITY FIX: April 8, 2009</strong>
+<li id="p016_openssl">
+<strong>016: SECURITY FIX: April 14, 2010</strong>
 &nbsp; <i>All architectures</i><br>
-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.
+In TLS connections, certain incorrectly formatted records can cause
+an OpenSSL client or server to crash due to a read attempt at NULL.
 <br>
-<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/001_openssl.patch">
+<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/016_openssl.patch">
 A source code patch exists which remedies this problem.</a>
 <p>