www/errata64.html

382 lines
12 KiB
HTML

<!doctype html>
<html lang=en id=errata>
<meta charset=utf-8>
<title>OpenBSD 6.4 Errata</title>
<meta name="description" content="the OpenBSD errata page">
<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/errata64.html">
<!--
IMPORTANT REMINDER
IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->
<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
6.4 Errata
</h2>
<hr>
For errata on a certain release, click below:<br>
<a href="errata20.html">2.0</a>,
<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>,
<br>
<a href="errata36.html">3.6</a>,
<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>,
<br>
<a href="errata52.html">5.2</a>,
<a href="errata53.html">5.3</a>,
<a href="errata54.html">5.4</a>,
<a href="errata55.html">5.5</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>,
<a href="errata62.html">6.2</a>,
<a href="errata63.html">6.3</a>,
<a href="errata65.html">6.5</a>,
<a href="errata66.html">6.6</a>,
<a href="errata67.html">6.7</a>,
<a href="errata68.html">6.8</a>,
<br>
<a href="errata69.html">6.9</a>,
<a href="errata70.html">7.0</a>,
<a href="errata71.html">7.1</a>,
<a href="errata72.html">7.2</a>,
<a href="errata73.html">7.3</a>.
<hr>
<p>
Patches for the OpenBSD base system are distributed as unified diffs.
Each patch is cryptographically signed with the
<a href="https://man.openbsd.org/OpenBSD-6.4/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/6.4.tar.gz">tar.gz file</a>
for convenience.
<p>
Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
utility can be used to apply binary updates on the following architectures:
amd64, i386, arm64.
<p>
Patches for supported releases are also incorporated into the
<a href="stable.html">-stable branch</a>.
<hr>
<ul>
<li id="p001_xserver">
<strong>001: SECURITY FIX: October 25, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
The Xorg X server incorrectly validates certain options, allowing arbitrary
files to be overwritten.
As an immediate (temporary) workaround, the Xorg binary can be disabled
by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p002_syspatch">
<strong>002: RELIABILITY FIX: November 2, 2018</strong>
&nbsp; <i>i386, amd64, arm64</i>
<br>
The syspatch utility incorrectly handles symbolic links.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p003_portsmash">
<strong>003: SECURITY FIX: November 17, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
The portsmash vulnerability allows exfiltration of elliptic curve keys.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p004_lockf">
<strong>004: RELIABILITY FIX: November 17, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
A recent change to POSIX file locks could cause incorrect results
during lock acquisition.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p005_perl">
<strong>005: SECURITY FIX: November 29, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Various overflows exist in perl.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p006_uipc">
<strong>006: RELIABILITY FIX: November 29, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
attempt excessive memory allocations leading to a crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p007_smtpd">
<strong>007: RELIABILITY FIX: November 29, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
The mail.mda and mail.lmtp delivery agents were not reporting temporary
failures correctly, causing smtpd to bounce messages in some cases where
it should have retried them.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p008_qcow2">
<strong>008: RELIABILITY FIX: November 29, 2018</strong>
&nbsp; <i>amd64 and i386</i>
<br>
Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p009_recvwait">
<strong>009: RELIABILITY FIX: December 20, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
While recv(2) with the MSG_WAITALL flag was receiving control
messages from a socket, the kernel could panic.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p010_pcbopts">
<strong>010: SECURITY FIX: December 22, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
The setsockopt(2) system call could overflow mbuf cluster kernel
memory by 4 bytes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p011_mincore">
<strong>011: SECURITY FIX: January 27, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
The mincore() system call can be used to observe memory access patterns
of other processes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p012_nfs">
<strong>012: RELIABILITY FIX: January 27, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Missing length checks in the NFS server and client can lead to crashes
and other errors.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p013_unveil">
<strong>013: SECURITY FIX: January 27, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
The unveil() system call can leak memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p014_pf6frag">
<strong>014: SECURITY FIX: March 1, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p015_pficmp">
<strong>015: SECURITY FIX: March 22, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
A state in pf could pass ICMP packets to a destination IP address
that did not match the state.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p016_vmmints">
<strong>016: SECURITY FIX: March 27, 2019</strong>
&nbsp; <i>amd64 and i386</i>
<br>
GDT and IDT limits were improperly restored during VMM context switches.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p017_rip6cksum">
<strong>017: RELIABILITY FIX: May 3, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
If a userland program sets the IPv6 checksum offset on a raw socket,
an incoming packet could crash the kernel. ospf6d is such a program.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/017_rip6cksum.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p018_mds">
<strong>018: SECURITY FIX: May 29, 2019</strong>
&nbsp; <i>amd64</i>
<br>
Intel CPUs have a cross privilege side-channel attack (MDS).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/018_mds.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p019_tcpsack">
<strong>019: RELIABILITY FIX: July 25, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
By creating long chains of TCP SACK holes, an attacker could possibly
slow down the system temporarily.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/019_tcpsack.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p020_smtpd">
<strong>020: RELIABILITY FIX: August 2, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
smtpd can crash on excessively large input, causing a denial of service.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/020_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p021_swapgs">
<strong>021: SECURITY FIX: August 9, 2019</strong>
&nbsp; <i>amd64</i>
<br>
Intel CPUs have another cross privilege side-channel attack. (SWAPGS)
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/021_swapgs.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p022_resume">
<strong>022: RELIABILITY FIX: September 2, 2019</strong>
&nbsp; <i>amd64</i>
<br>
Resume forgot to restore MSR/PAT configuration.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/022_resume.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p023_frag6ecn">
<strong>023: RELIABILITY FIX: September 2, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
When processing ECN bits on incoming IPv6 fragments, the kernel
could crash. Per default pf fragment reassemble prevents the crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/023_frag6ecn.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p024_expat">
<strong>024: SECURITY FIX: September 14, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Libexpat 2.2.6 was affected by the heap overflow CVE-2019-15903.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/024_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p025_unbound">
<strong>025: RELIABILITY FIX: October 5, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Specially crafted queries may crash unwind and unbound.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/025_unbound.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p026_dhcpd">
<strong>026: SECURITY FIX: October 5, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
dhcpd leaks 4 bytes of stack to the network.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/026_dhcpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
</ul>
<hr>