errata62.html

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

<title>OpenBSD 6.2 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/errata62.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.2 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="errata63.html">6.3</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.2/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.2.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_tcb_invalid">
<strong>001: RELIABILITY FIX: October 13, 2017</strong>
&nbsp; <i>amd64</i>
<br>
A local user could trigger a kernel panic by using an invalid TCB value.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/001_tcb_invalid.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p002_fktrace">
<strong>002: SECURITY FIX: December 1, 2017</strong>
&nbsp; <i>All architectures</i>
<br>
The fktrace(2) system call had insufficient security checks.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/002_fktrace.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_mpls">
<strong>003: RELIABILITY FIX: December 10, 2017</strong>
&nbsp; <i>All architectures</i>
<br>
A number of bugs were discovered in the MPLS stack that can be used to
remotely trigger kernel crashes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/003_mpls.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_libssl">
<strong>004: RELIABILITY FIX: January 14, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
An incorrect TLS extensions block is generated when no extensions are present,
which can result in handshake failures.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/004_libssl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_ahopts">
<strong>005: RELIABILITY FIX: February 2, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Specially crafted IPsec AH packets with IP options or IPv6 extension
headers could crash or hang the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/005_ahopts.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_prevhdr">
<strong>006: RELIABILITY FIX: February 2, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
Processing IPv6 fragments could incorrectly access memory of an mbuf
chain that is not within an mbuf.  This may crash the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/006_prevhdr.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_etherip">
<strong>007: SECURITY FIX: February 2, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
If the EtherIP tunnel protocol was disabled, IPv6 packets were not
discarded properly.  This causes a double free in the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/007_etherip.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_unbound">
<strong>008: SECURITY FIX: February 8, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
A flaw was found in the way unbound validated wildcard-synthesized
NSEC records. An improperly validated wildcard NSEC record could be
used to prove the non-existence (NXDOMAIN answer) of an existing
wildcard record, or trick unbound into accepting a NODATA proof.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/008_unbound.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_meltdown">
<strong>009: SECURITY FIX: March 1, 2018</strong>
&nbsp; <i>amd64</i>
<br>
Intel CPUs contain a speculative execution flaw called Meltdown which
allows userspace programs to access kernel memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/009_meltdown.patch.sig">
A complex workaround solves this problem.</a>
<p>

<li id="p010_ahauth">
<strong>010: RELIABILITY FIX: March 20, 2018</strong>
&nbsp; <i>All architectures</i>
<br>
The IPsec AH header could be longer than the network packet, resulting in
a kernel crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/010_ahauth.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

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

<li id="p012_httpd">
<strong>012: 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.2/common/012_httpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_ipseclen">
<strong>013: 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.2/common/013_ipseclen.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_ipsecout">
<strong>014: 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.2/common/014_ipsecout.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_libcrypto">
<strong>015: 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.2/common/015_libcrypto.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

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

<li id="p017_intelfpu">
<strong>017: SECURITY FIX: June 21, 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.2/common/017_intelfpu.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_execsize">
<strong>018: 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.2/common/018_execsize.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_amdlfence">
<strong>019: 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.2/common/019_amdlfence.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

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

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

<li id="p022_fpufork">
<strong>022: 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.2/common/022_fpufork.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

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

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

</ul>

<hr>