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

File: [local] / www / errata55.html (download) (as text)

Revision 1.53, Tue Mar 28 06:41:18 2017 UTC (7 years, 1 month ago) by tb
Branch: MAIN
Changes since 1.52: +29 -29 lines

fix a ton of broken or incorrect man links by normalizing them.
fix invalid html to make the w3c validator happy.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 5.5 Errata</title>
<meta name="description" content="the OpenBSD CD errata page">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/errata55.html">
</head>

<!--
			IMPORTANT REMINDER
	IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->


<body bgcolor="#ffffff" text="#000000" link="#23238E">

<h2>
<a href="index.html">
<font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
<font color="#e00000">5.5 Errata</font>
</h2>
<hr>

For errata on a certain release, click below:<br>
<a href="errata21.html">2.1</a>,
<a href="errata22.html">2.2</a>,
<a href="errata23.html">2.3</a>,
<a href="errata24.html">2.4</a>,
<a href="errata25.html">2.5</a>,
<a href="errata26.html">2.6</a>,
<a href="errata27.html">2.7</a>,
<a href="errata28.html">2.8</a>,
<a href="errata29.html">2.9</a>,
<a href="errata30.html">3.0</a>,
<a href="errata31.html">3.1</a>,
<a href="errata32.html">3.2</a>,
<a href="errata33.html">3.3</a>,
<a href="errata34.html">3.4</a>,
<a href="errata35.html">3.5</a>,
<a href="errata36.html">3.6</a>,
<br>
<a href="errata37.html">3.7</a>,
<a href="errata38.html">3.8</a>,
<a href="errata39.html">3.9</a>,
<a href="errata40.html">4.0</a>,
<a href="errata41.html">4.1</a>,
<a href="errata42.html">4.2</a>,
<a href="errata43.html">4.3</a>,
<a href="errata44.html">4.4</a>,
<a href="errata45.html">4.5</a>,
<a href="errata46.html">4.6</a>,
<a href="errata47.html">4.7</a>,
<a href="errata48.html">4.8</a>,
<a href="errata49.html">4.9</a>,
<a href="errata50.html">5.0</a>,
<a href="errata51.html">5.1</a>,
<a href="errata52.html">5.2</a>,
<br>
<a href="errata53.html">5.3</a>,
<a href="errata54.html">5.4</a>,
<a href="errata56.html">5.6</a>,
<a href="errata57.html">5.7</a>,
<a href="errata58.html">5.8</a>,
<a href="errata59.html">5.9</a>,
<a href="errata60.html">6.0</a>,
<a href="errata61.html">6.1</a>.
<hr>

<p>
Patches for the OpenBSD base system are distributed as unified diffs.
Each patch is cryptographically signed with the
<a href="http://man.openbsd.org/OpenBSD-5.5/signify.1">signify(1)</a> tool and contains
usage instructions.
All the following patches are also available in one
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5.tar.gz">tar.gz file</a>
for convenience.

<p>
Patches for supported releases are also incorporated into the
<a href="stable.html">-stable branch</a>.

<hr>

<ul>

<li id="p001_icmp">
<font color="#009000"><strong>001: RELIABILITY FIX: March 15, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Memory corruption happens during
ICMP reflection handling.  ICMP reflection is disabled by default.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/001_icmp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p002_openssl">
<font color="#009000"><strong>002: SECURITY FIX: April 8, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Missing bounds checking in OpenSSL's implementation of the TLS/DTLS
heartbeat extension (RFC6520) which can result in a leak of memory contents.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/002_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_ftp">
<font color="#009000"><strong>003: SECURITY FIX: April 9, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Missing hostname check for HTTPS connections in the
<a href="http://man.openbsd.org/OpenBSD-5.5/ftp.1">ftp(1)</a>
utility.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/003_ftp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_openssl">
<font color="#009000"><strong>004: SECURITY FIX: April 12, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
A use-after-free race condition in OpenSSL's read buffer may permit an attacker
to inject data from one connection into another.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/004_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_openssl">
<font color="#009000"><strong>005: RELIABILITY FIX: May 1, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
An attacker can trigger generation of an SSL alert which could cause
a null pointer dereference.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/005_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_libXfont">
<font color="#009000"><strong>006: SECURITY FIX: May 24, 2014</strong></font>
&nbsp; <i>All architectures with X server</i><br>
X Font Service Protocol & Font metadata file handling issues in libXfont
<ul>
<li>CVE-2014-0209: integer overflow of allocations in font metadata file parsing
<li>CVE-2014-0210: unvalidated length fields when parsing xfs protocol replies
<li>CVE-2014-0211: integer overflows calculating memory needs for xfs replies
</ul>
Please see <a href="http://lists.x.org/archives/xorg-announce/2014-May/002431.html">the advisory</a> for more information.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/006_libXfont.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_sendmail">
<font color="#009000"><strong>007: SECURITY FIX: June 5, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Sendmail was not properly closing file descriptions before executing programs.
This could enable local users to interfere with an open SMTP connection.
This issue was assigned CVE-2014-3956.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/007_sendmail.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_openssl">
<font color="#009000"><strong>008: SECURITY FIX: June 6, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
This patch contains a number of SSL library fixes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/008_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_dhcp">
<font color="#009000"><strong>009: RELIABILITY FIX: July 30, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Packets with illegal DHCP options can lead to memory exhaustion of
<a href="http://man.openbsd.org/OpenBSD-5.5/dhclient.8">dhclient(8)</a>
and
<a href="http://man.openbsd.org/OpenBSD-5.5/dhcpd.8">dhcpd(8)</a>.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/009_dhcp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p010_openssl">
<font color="#009000"><strong>010: SECURITY FIX: August 9, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
This patch contains a number of SSL library fixes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/010_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p011_nginx">
<font color="#009000"><strong>011: SECURITY FIX: October 1, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
nginx can reuse cached SSL sessions in unrelated contexts, allowing virtual
host confusion attacks in some configurations.
This issue was assigned CVE-2014-3616.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/011_nginx.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p012_openssl">
<font color="#009000"><strong>012: RELIABILITY FIX: October 20, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Two remotely triggerable memory leaks in OpenSSL can lead to a denial of
service in server applications.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/012_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_kernexec">
<font color="#009000"><strong>013: RELIABILITY FIX: October 20, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Executable headers with an unaligned address will trigger a kernel panic.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/013_kernexec.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_pfctl">
<font color="#009000"><strong>014: RELIABILITY FIX: November 17, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
A PF rule using an IPv4 address
followed by an IPv6 address and then a dynamic address, e.g. "pass
from {192.0.2.1 2001:db8::1} to (pppoe0)", will have an incorrect /32
mask applied to the dynamic address.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/014_pfctl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_asr">
<font color="#009000"><strong>015: RELIABILITY FIX: November 17, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Querying an invalid hostname with gethostbyname(3) could cause a NULL deref.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/015_asr.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p016_pipex">
<font color="#009000"><strong>016: RELIABILITY FIX: December 5, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Several bugs were fixed that allowed a crash from remote when an active pipex
session exists.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/016_pipex.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p017_pppoe">
<font color="#009000"><strong>017: RELIABILITY FIX: December 5, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
An incorrect memcpy call would result in corrupted MAC addresses when
using PPPOE.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/017_pppoe.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_virtio">
<font color="#009000"><strong>018: RELIABILITY FIX: December 9, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
Several bugs in virtio(4) can lead to hangs with virtio devices,
like vio(4) and vioblk(4).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/018_virtio.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_xserver">
<font color="#009000"><strong>019: SECURITY FIX: December 9, 2014</strong></font>
&nbsp; <i>All architectures</i><br>
One year after Ilja van Sprundel discovered and reported a large number
of issues in the way the X server code base handles requests from X clients,
they have been fixed.
<br>
<a href="http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/">X Advisory</a>
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/019_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p020_libevent">
<font color="#009000"><strong>020: SECURITY FIX: January 13, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Fix CVE-2014-6272 in libevent 1.4 event buffer handling.  OpenBSD
base uses it for the programs: cu tmux ftp-proxy httpd ldapd relayd
tftp-proxy tftpd
<br>
<a href="http://www.wangafu.net/~nickm/volatile/advisory.txt.asc">Libevent Advisory</a>
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/020_libevent.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p021_xserver">
<font color="#009000"><strong>021: SECURITY FIX: March 3, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Information leak in the XkbSetGeometry request of X servers.
<br>
For more information, see the
<a href="http://www.x.org/wiki/Development/Security/Advisory-2015-02-10/">X.org advisory</a>.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/021_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p022_freetype">
<font color="#009000"><strong>022: SECURITY FIX: March 13, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Another fix for buffer overflows in malformed fonts.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/022_freetype.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p023_libxfont">
<font color="#009000"><strong>023: SECURITY FIX: March 18, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Buffer overflows in libXfont
<br>
For more information, see the
<a href="http://www.x.org/wiki/Development/Security/Advisory-2015-03-17/">X.org advisory</a>.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/023_libxfont.patch.sig">
A source code patch exists which remedies this problem.</a>
<br>Note that the instructions should read <code>cd /usr/xenocara/lib/libXfont</code>.
<p>

<li id="p024_openssl">
<font color="#009000"><strong>024: SECURITY FIX: March 19, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Fix two possible crash causing defects.<br>
CVE-2015-0286 - Apply fix from OpenSSL for ASN1_TYPE_cmp.<br>
CVE-2015-0292 - Backport existing fix for Base64 decoding.<br>
<br>
For more information, see the
<a href="https://www.openssl.org/news/secadv_20150319.txt">OpenSSL advisory</a>.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/024_openssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<br>Note that instructions should read <code>cd /usr/src/lib/libssl/crypto</code>.
<p>

<li id="p025_smtpd">
<font color="#009000"><strong>025: RELIABILITY FIX: April 17, 2015</strong></font>
&nbsp; <i>All architectures</i><br>
Fix a logic error in smtpd handling of SNI.
This could allow a remote user to crash the server or provoke a disconnect of other sessions.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/025_smtpd.patch.sig">
  A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>

</body>
</html>