errata63.html

<!doctype html>
<html lang=en id=errata>
<meta charset=utf-8>

<title>OpenBSD 6.3 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/errata63.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.3 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="errata64.html">6.4</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>,
<a href="errata74.html">7.4</a>,
<a href="errata75.html">7.5</a>,
<a href="errata76.html">7.6</a>,
<a href="errata77.html">7.7</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.3/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.3.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_perl">
<strong>001: SECURITY FIX: April 14, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Heap overflows exist in perl which can lead to segmentation faults,
crashes, and reading memory past the buffer.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/001_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p002_libtls">
<strong>002: RELIABILITY FIX: April 21, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Additional data is inadvertently removed when private keys are cleared from
TLS configuration, which can prevent OCSP from functioning correctly.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/002_libtls.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_arp">
<strong>003: RELIABILITY FIX: April 21, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
ARP replies could be sent on the wrong member of a bridge(4) interface.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/003_arp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_gif">
<strong>004: SECURITY FIX: April 21, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
In the gif(4) interface, use the specified protocol for IPv6, plug
a mbuf leak and avoid a use after free.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/004_gif.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_httpd">
<strong>005: RELIABILITY FIX: April 21, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
httpd can leak file descriptors when servicing range requests.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/005_httpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_ipseclen">
<strong>006: RELIABILITY FIX: May 8, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Incorrect handling of fragmented IPsec packets could result in a system crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/006_ipseclen.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_libcrypto">
<strong>007: RELIABILITY FIX: May 8, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Incorrect checks in libcrypto can prevent Diffie-Hellman Exchange operations
from working.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/007_libcrypto.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_ipsecout">
<strong>008: RELIABILITY FIX: May 17, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
A malicious packet can cause a kernel crash when using IPsec over IPv6.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/008_ipsecout.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_libcrypto">
<strong>009: SECURITY FIX: June 14, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
DSA and ECDSA signature generation can potentially leak secret information
to a timing side-channel attack.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/009_libcrypto.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p010_intelfpu">
<strong>010: SECURITY FIX: June 17, 2018</strong>
&nbsp; <i>amd64</i>
<br>
Intel CPUs speculatively access FPU registers even when the FPU is disabled,
so data (including AES keys) from previous contexts could be discovered
if using the lazy-save approach.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p011_perl">
<strong>011: SECURITY FIX: June 21, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Perl's Archive::Tar module could be made to write files outside of
its working directory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/011_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p012_execsize">
<strong>012: RELIABILITY FIX: July 25, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
A regular user could trigger a kernel panic by executing an invalid
ELF binary.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/012_execsize.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_ipsecexpire">
<strong>013: RELIABILITY FIX: July 25, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
When an IPsec key expired, the kernel could panic due to unfinished
timeout tasks.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/013_ipsecexpire.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_amdlfence">
<strong>014: SECURITY FIX: July 31, 2018</strong>
&nbsp; <i>amd64 and i386</i>
<br>
On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
instruction against speculation.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/014_amdlfence.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_ioport">
<strong>015: SECURITY FIX: July 31, 2018</strong>
&nbsp; <i>i386</i>
<br>
IO port permissions were incorrectly restricted.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/015_ioport.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p016_fpuinit">
<strong>016: RELIABILITY FIX: August 4, 2018</strong>
&nbsp; <i>amd64</i>
<br>
Incorrect initialization of the FPU caused floating point exceptions
when running on Xen.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p017_fpufork">
<strong>017: SECURITY FIX: August 24, 2018</strong>
&nbsp; <i>amd64</i>
<br>
State from the FPU of one userland process could be exposed to other processes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_vmml1tf">
<strong>018: SECURITY FIX: August 24, 2018</strong>
&nbsp; <i>amd64</i>
<br>
The Intel L1TF bug allows a vmm guest to read host memory.
Install the CPU firmware using fw_update(1) and apply this workaround.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_ldtr">
<strong>019: SECURITY FIX: September 21, 2018</strong>
&nbsp; <i>amd64</i>
<br>
On AMD CPUs, LDTR must be managed crossing between VMs.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/019_ldtr.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p020_xserver">
<strong>020: 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.3/common/020_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p021_syspatch">
<strong>021: 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.3/common/021_syspatch.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p022_blinding">
<strong>022: SECURITY FIX: November 17, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Timing side channels may leak information about DSA and ECDSA private keys.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/022_blinding.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p023_lockf">
<strong>023: 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.3/common/023_lockf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p024_perl">
<strong>024: 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.3/common/024_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p025_uipc">
<strong>025: 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.3/common/025_uipc.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p026_recvwait">
<strong>026: 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.3/common/026_recvwait.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p027_pcbopts">
<strong>027: 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.3/common/027_pcbopts.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p028_mincore">
<strong>028: SECURITY FIX: February 5, 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.3/common/028_mincore.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p029_nfs">
<strong>029: RELIABILITY FIX: February 5, 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.3/common/029_nfs.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p030_pf6frag">
<strong>030: 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.3/common/030_pf6frag.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p031_pficmp">
<strong>031: 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.3/common/031_pficmp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p032_vmmints">
<strong>032: 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.3/common/032_vmmints.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p033_rip6cksum">
<strong>033: 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.3/common/033_rip6cksum.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>