Annotation of www/errata62.html, Revision 1.9
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.2 Errata</title>
5: <meta name="description" content="the OpenBSD errata page">
6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
9: <link rel="canonical" href="https://www.openbsd.org/errata62.html">
10: </head>
11:
12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16: <body bgcolor="#ffffff" text="#000000" link="#23238E">
17:
18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">6.2 Errata</font>
22: </h2>
23: <hr>
24:
25: For errata on a certain release, click below:<br>
26: <a href="errata21.html">2.1</a>,
27: <a href="errata22.html">2.2</a>,
28: <a href="errata23.html">2.3</a>,
29: <a href="errata24.html">2.4</a>,
30: <a href="errata25.html">2.5</a>,
31: <a href="errata26.html">2.6</a>,
32: <a href="errata27.html">2.7</a>,
33: <a href="errata28.html">2.8</a>,
34: <a href="errata29.html">2.9</a>,
35: <a href="errata30.html">3.0</a>,
36: <a href="errata31.html">3.1</a>,
37: <a href="errata32.html">3.2</a>,
38: <a href="errata33.html">3.3</a>,
39: <a href="errata34.html">3.4</a>,
40: <a href="errata35.html">3.5</a>,
41: <a href="errata36.html">3.6</a>,
42: <br>
43: <a href="errata37.html">3.7</a>,
44: <a href="errata38.html">3.8</a>,
45: <a href="errata39.html">3.9</a>,
46: <a href="errata40.html">4.0</a>,
47: <a href="errata41.html">4.1</a>,
48: <a href="errata42.html">4.2</a>,
49: <a href="errata43.html">4.3</a>,
50: <a href="errata44.html">4.4</a>,
51: <a href="errata45.html">4.5</a>,
52: <a href="errata46.html">4.6</a>,
53: <a href="errata47.html">4.7</a>,
54: <a href="errata48.html">4.8</a>,
55: <a href="errata49.html">4.9</a>,
56: <a href="errata50.html">5.0</a>,
57: <a href="errata51.html">5.1</a>,
58: <a href="errata52.html">5.2</a>,
59: <br>
60: <a href="errata53.html">5.3</a>,
61: <a href="errata54.html">5.4</a>,
62: <a href="errata55.html">5.5</a>,
63: <a href="errata56.html">5.6</a>,
64: <a href="errata57.html">5.7</a>,
65: <a href="errata58.html">5.8</a>,
66: <a href="errata59.html">5.9</a>,
67: <a href="errata60.html">6.0</a>,
68: <a href="errata61.html">6.1</a>.
69: <hr>
70:
71: <p>
72: Patches for the OpenBSD base system are distributed as unified diffs.
73: Each patch is cryptographically signed with the
74: <a href="https://man.openbsd.org/OpenBSD-6.2/signify.1">signify(1)</a> tool and contains
75: usage instructions.
76: All the following patches are also available in one
77: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2.tar.gz">tar.gz file</a>
78: for convenience.
79:
80: <p>
81: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
82: utility can be used to apply binary updates on the following architectures:
1.3 tj 83: amd64, i386, arm64.
1.1 deraadt 84:
85: <p>
86: Patches for supported releases are also incorporated into the
87: <a href="stable.html">-stable branch</a>, which is maintained for one year
88: after release.
89:
90: <hr>
91:
92: <ul>
93:
1.2 bluhm 94: <li id="p001_tcb_invalid">
95: <font color="#009000">
96: <strong>001: RELIABILITY FIX: October 13, 2017</strong></font>
97: <i>amd64</i>
98: <br>
99: A local user could trigger a kernel panic by using an invalid TCB value.
100: <br>
101: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/001_tcb_invalid.patch.sig">
1.3 tj 102: A source code patch exists which remedies this problem.</a>
103: <p>
104:
105: <li id="p002_fktrace">
106: <font color="#009000">
107: <strong>002: SECURITY FIX: December 1, 2017</strong></font>
108: <i>All architectures</i>
109: <br>
110: The fktrace(2) system call had insufficient security checks.
111: <br>
112: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/002_fktrace.patch.sig">
1.2 bluhm 113: A source code patch exists which remedies this problem.</a>
114: <p>
1.1 deraadt 115:
1.4 tj 116: <li id="p003_mpls">
117: <font color="#009000">
118: <strong>003: RELIABILITY FIX: December 10, 2017</strong></font>
119: <i>All architectures</i>
120: <br>
121: A number of bugs were discovered in the MPLS stack that can be used to
122: remotely trigger kernel crashes.
123: <br>
124: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/003_mpls.patch.sig">
125: A source code patch exists which remedies this problem.</a>
126: <p>
127:
1.5 tj 128: <li id="p004_libssl">
129: <font color="#009000">
130: <strong>004: RELIABILITY FIX: January 14, 2018</strong></font>
131: <i>All architectures</i>
132: <br>
133: An incorrect TLS extensions block is generated when no extensions are present,
134: which can result in handshake failures.
135: <br>
136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/004_libssl.patch.sig">
137: A source code patch exists which remedies this problem.</a>
138: <p>
139:
1.6 tj 140: <li id="p005_ahopts">
141: <font color="#009000">
142: <strong>005: RELIABILITY FIX: February 2, 2018</strong></font>
143: <i>All architectures</i>
144: <br>
145: Specially crafted IPsec AH packets with IP options or IPv6 extension
146: headers could crash or hang the kernel.
147: <br>
148: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/005_ahopts.patch.sig">
149: A source code patch exists which remedies this problem.</a>
150: <p>
151:
152: <li id="p006_prevhdr">
153: <font color="#009000">
154: <strong>006: RELIABILITY FIX: February 2, 2018</strong></font>
155: <i>All architectures</i>
156: <br>
157: Processing IPv6 fragments could incorrectly access memory of an mbuf
158: chain that is not within an mbuf. This may crash the kernel.
159: <br>
160: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/006_prevhdr.patch.sig">
161: A source code patch exists which remedies this problem.</a>
162: <p>
163:
164: <li id="p007_etherip">
165: <font color="#009000">
166: <strong>007: SECURITY FIX: February 2, 2018</strong></font>
167: <i>All architectures</i>
168: <br>
169: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
170: discarded properly. This causes a double free in the kernel.
171: <br>
172: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/007_etherip.patch.sig">
173: A source code patch exists which remedies this problem.</a>
174: <p>
175:
1.7 tj 176: <li id="p008_unbound">
177: <font color="#009000">
1.8 tj 178: <strong>008: SECURITY FIX: February 8, 2018</strong></font>
1.7 tj 179: <i>All architectures</i>
180: <br>
181: A flaw was found in the way unbound validated wildcard-synthesized
182: NSEC records. An improperly validated wildcard NSEC record could be
183: used to prove the non-existence (NXDOMAIN answer) of an existing
184: wildcard record, or trick unbound into accepting a NODATA proof.
185: <br>
186: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/008_unbound.patch.sig">
187: A source code patch exists which remedies this problem.</a>
188: <p>
189:
1.9 ! tj 190: <li id="p009_meltdown">
! 191: <font color="#009000">
! 192: <strong>009: SECURITY FIX: March 1, 2018</strong></font>
! 193: <i>amd64</i>
! 194: <br>
! 195: Intel CPUs contain a speculative execution flaw called Meltdown which
! 196: allows userspace programs to access kernel memory.
! 197: <br>
! 198: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/009_meltdown.patch.sig">
! 199: A complex workaround solves this problem.</a>
! 200: <p>
! 201:
1.1 deraadt 202: </ul>
203:
204: <hr>
205:
206: </body>
207: </html>