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

Annotation of www/errata62.html, Revision 1.40

1.29      bentley     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
1.1       deraadt     5: <title>OpenBSD 6.2 Errata</title>
                      6: <meta name="description" content="the OpenBSD errata page">
                      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:
                     11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
1.29      bentley    16: <h2 id=OpenBSD>
1.1       deraadt    17: <a href="index.html">
1.29      bentley    18: <i>Open</i><b>BSD</b></a>
                     19: 6.2 Errata
1.1       deraadt    20: </h2>
                     21: <hr>
                     22:
                     23: For errata on a certain release, click below:<br>
1.31      schwarze   24: <a href="errata20.html">2.0</a>,
1.1       deraadt    25: <a href="errata21.html">2.1</a>,
                     26: <a href="errata22.html">2.2</a>,
                     27: <a href="errata23.html">2.3</a>,
                     28: <a href="errata24.html">2.4</a>,
                     29: <a href="errata25.html">2.5</a>,
                     30: <a href="errata26.html">2.6</a>,
                     31: <a href="errata27.html">2.7</a>,
                     32: <a href="errata28.html">2.8</a>,
                     33: <a href="errata29.html">2.9</a>,
                     34: <a href="errata30.html">3.0</a>,
                     35: <a href="errata31.html">3.1</a>,
                     36: <a href="errata32.html">3.2</a>,
                     37: <a href="errata33.html">3.3</a>,
                     38: <a href="errata34.html">3.4</a>,
                     39: <a href="errata35.html">3.5</a>,
1.31      schwarze   40: <br>
1.1       deraadt    41: <a href="errata36.html">3.6</a>,
                     42: <a href="errata37.html">3.7</a>,
                     43: <a href="errata38.html">3.8</a>,
                     44: <a href="errata39.html">3.9</a>,
                     45: <a href="errata40.html">4.0</a>,
                     46: <a href="errata41.html">4.1</a>,
                     47: <a href="errata42.html">4.2</a>,
                     48: <a href="errata43.html">4.3</a>,
                     49: <a href="errata44.html">4.4</a>,
                     50: <a href="errata45.html">4.5</a>,
                     51: <a href="errata46.html">4.6</a>,
                     52: <a href="errata47.html">4.7</a>,
                     53: <a href="errata48.html">4.8</a>,
                     54: <a href="errata49.html">4.9</a>,
                     55: <a href="errata50.html">5.0</a>,
                     56: <a href="errata51.html">5.1</a>,
1.31      schwarze   57: <br>
1.1       deraadt    58: <a href="errata52.html">5.2</a>,
                     59: <a href="errata53.html">5.3</a>,
                     60: <a href="errata54.html">5.4</a>,
                     61: <a href="errata55.html">5.5</a>,
                     62: <a href="errata56.html">5.6</a>,
                     63: <a href="errata57.html">5.7</a>,
                     64: <a href="errata58.html">5.8</a>,
                     65: <a href="errata59.html">5.9</a>,
                     66: <a href="errata60.html">6.0</a>,
1.11      deraadt    67: <a href="errata61.html">6.1</a>,
1.26      deraadt    68: <a href="errata63.html">6.3</a>,
1.28      deraadt    69: <a href="errata64.html">6.4</a>,
1.30      deraadt    70: <a href="errata65.html">6.5</a>,
1.32      deraadt    71: <a href="errata66.html">6.6</a>,
1.33      deraadt    72: <a href="errata67.html">6.7</a>,
1.34      deraadt    73: <a href="errata68.html">6.8</a>,
1.35      tj         74: <br>
1.36      deraadt    75: <a href="errata69.html">6.9</a>,
1.37      deraadt    76: <a href="errata70.html">7.0</a>,
1.38      deraadt    77: <a href="errata71.html">7.1</a>,
1.39      tj         78: <a href="errata72.html">7.2</a>,
1.40    ! tj         79: <a href="errata73.html">7.3</a>,
        !            80: <a href="errata74.html">7.4</a>.
1.1       deraadt    81: <hr>
                     82:
                     83: <p>
                     84: Patches for the OpenBSD base system are distributed as unified diffs.
                     85: Each patch is cryptographically signed with the
                     86: <a href="https://man.openbsd.org/OpenBSD-6.2/signify.1">signify(1)</a> tool and contains
                     87: usage instructions.
                     88: All the following patches are also available in one
                     89: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2.tar.gz">tar.gz file</a>
                     90: for convenience.
                     91:
                     92: <p>
                     93: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
                     94: utility can be used to apply binary updates on the following architectures:
1.3       tj         95: amd64, i386, arm64.
1.1       deraadt    96:
                     97: <p>
                     98: Patches for supported releases are also incorporated into the
1.27      tj         99: <a href="stable.html">-stable branch</a>.
1.1       deraadt   100:
                    101: <hr>
                    102:
                    103: <ul>
                    104:
1.2       bluhm     105: <li id="p001_tcb_invalid">
1.29      bentley   106: <strong>001: RELIABILITY FIX: October 13, 2017</strong>
1.2       bluhm     107: &nbsp; <i>amd64</i>
                    108: <br>
                    109: A local user could trigger a kernel panic by using an invalid TCB value.
                    110: <br>
                    111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/001_tcb_invalid.patch.sig">
1.3       tj        112: A source code patch exists which remedies this problem.</a>
                    113: <p>
                    114:
                    115: <li id="p002_fktrace">
1.29      bentley   116: <strong>002: SECURITY FIX: December 1, 2017</strong>
1.3       tj        117: &nbsp; <i>All architectures</i>
                    118: <br>
                    119: The fktrace(2) system call had insufficient security checks.
                    120: <br>
                    121: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/002_fktrace.patch.sig">
1.2       bluhm     122: A source code patch exists which remedies this problem.</a>
                    123: <p>
1.1       deraadt   124:
1.4       tj        125: <li id="p003_mpls">
1.29      bentley   126: <strong>003: RELIABILITY FIX: December 10, 2017</strong>
1.4       tj        127: &nbsp; <i>All architectures</i>
                    128: <br>
                    129: A number of bugs were discovered in the MPLS stack that can be used to
                    130: remotely trigger kernel crashes.
                    131: <br>
                    132: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/003_mpls.patch.sig">
                    133: A source code patch exists which remedies this problem.</a>
                    134: <p>
                    135:
1.5       tj        136: <li id="p004_libssl">
1.29      bentley   137: <strong>004: RELIABILITY FIX: January 14, 2018</strong>
1.5       tj        138: &nbsp; <i>All architectures</i>
                    139: <br>
                    140: An incorrect TLS extensions block is generated when no extensions are present,
                    141: which can result in handshake failures.
                    142: <br>
                    143: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/004_libssl.patch.sig">
                    144: A source code patch exists which remedies this problem.</a>
                    145: <p>
                    146:
1.6       tj        147: <li id="p005_ahopts">
1.29      bentley   148: <strong>005: RELIABILITY FIX: February 2, 2018</strong>
1.6       tj        149: &nbsp; <i>All architectures</i>
                    150: <br>
                    151: Specially crafted IPsec AH packets with IP options or IPv6 extension
                    152: headers could crash or hang the kernel.
                    153: <br>
                    154: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/005_ahopts.patch.sig">
                    155: A source code patch exists which remedies this problem.</a>
                    156: <p>
                    157:
                    158: <li id="p006_prevhdr">
1.29      bentley   159: <strong>006: RELIABILITY FIX: February 2, 2018</strong>
1.6       tj        160: &nbsp; <i>All architectures</i>
                    161: <br>
                    162: Processing IPv6 fragments could incorrectly access memory of an mbuf
                    163: chain that is not within an mbuf.  This may crash the kernel.
                    164: <br>
                    165: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/006_prevhdr.patch.sig">
                    166: A source code patch exists which remedies this problem.</a>
                    167: <p>
                    168:
                    169: <li id="p007_etherip">
1.29      bentley   170: <strong>007: SECURITY FIX: February 2, 2018</strong>
1.6       tj        171: &nbsp; <i>All architectures</i>
                    172: <br>
                    173: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
                    174: discarded properly.  This causes a double free in the kernel.
                    175: <br>
                    176: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/007_etherip.patch.sig">
                    177: A source code patch exists which remedies this problem.</a>
                    178: <p>
                    179:
1.7       tj        180: <li id="p008_unbound">
1.29      bentley   181: <strong>008: SECURITY FIX: February 8, 2018</strong>
1.7       tj        182: &nbsp; <i>All architectures</i>
                    183: <br>
                    184: A flaw was found in the way unbound validated wildcard-synthesized
                    185: NSEC records. An improperly validated wildcard NSEC record could be
                    186: used to prove the non-existence (NXDOMAIN answer) of an existing
                    187: wildcard record, or trick unbound into accepting a NODATA proof.
                    188: <br>
                    189: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/008_unbound.patch.sig">
                    190: A source code patch exists which remedies this problem.</a>
                    191: <p>
                    192:
1.9       tj        193: <li id="p009_meltdown">
1.29      bentley   194: <strong>009: SECURITY FIX: March 1, 2018</strong>
1.9       tj        195: &nbsp; <i>amd64</i>
                    196: <br>
                    197: Intel CPUs contain a speculative execution flaw called Meltdown which
                    198: allows userspace programs to access kernel memory.
                    199: <br>
                    200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/009_meltdown.patch.sig">
                    201: A complex workaround solves this problem.</a>
                    202: <p>
                    203:
1.10      tj        204: <li id="p010_ahauth">
1.29      bentley   205: <strong>010: RELIABILITY FIX: March 20, 2018</strong>
1.10      tj        206: &nbsp; <i>All architectures</i>
                    207: <br>
                    208: The IPsec AH header could be longer than the network packet, resulting in
                    209: a kernel crash.
                    210: <br>
                    211: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/010_ahauth.patch.sig">
                    212: A source code patch exists which remedies this problem.</a>
                    213: <p>
                    214:
1.12      afresh1   215: <li id="p011_perl">
1.29      bentley   216: <strong>011: SECURITY FIX: April 14, 2018</strong>
1.12      afresh1   217: &nbsp; <i>All architectures</i>
                    218: <br>
                    219: Heap overflows exist in perl which can lead to segmentation faults,
                    220: crashes, and reading memory past the buffer.
                    221: <br>
                    222: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/011_perl.patch.sig">
                    223: A source code patch exists which remedies this problem.</a>
                    224: <p>
                    225:
1.13      tj        226: <li id="p012_httpd">
1.29      bentley   227: <strong>012: RELIABILITY FIX: April 21, 2018</strong>
1.13      tj        228: &nbsp; <i>All architectures</i>
                    229: <br>
                    230: httpd can leak file descriptors when servicing range requests.
                    231: <br>
                    232: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/012_httpd.patch.sig">
                    233: A source code patch exists which remedies this problem.</a>
                    234: <p>
                    235:
1.14      tj        236: <li id="p013_ipseclen">
1.29      bentley   237: <strong>013: RELIABILITY FIX: May 8, 2018</strong>
1.14      tj        238: &nbsp; <i>All architectures</i>
                    239: <br>
                    240: Incorrect handling of fragmented IPsec packets could result in a system crash.
                    241: <br>
                    242: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/013_ipseclen.patch.sig">
                    243: A source code patch exists which remedies this problem.</a>
                    244: <p>
                    245:
1.15      tj        246: <li id="p014_ipsecout">
1.29      bentley   247: <strong>014: RELIABILITY FIX: May 17, 2018</strong>
1.15      tj        248: &nbsp; <i>All architectures</i>
                    249: <br>
                    250: A malicious packet can cause a kernel crash when using IPsec over IPv6.
                    251: <br>
                    252: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/014_ipsecout.patch.sig">
                    253: A source code patch exists which remedies this problem.</a>
                    254: <p>
                    255:
1.16      tb        256: <li id="p015_libcrypto">
1.29      bentley   257: <strong>015: SECURITY FIX: June 14, 2018</strong>
1.16      tb        258: &nbsp; <i>All architectures</i>
                    259: <br>
                    260: DSA and ECDSA signature generation can potentially leak secret information
                    261: to a timing side-channel attack.
                    262: <br>
                    263: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/015_libcrypto.patch.sig">
                    264: A source code patch exists which remedies this problem.</a>
                    265: <p>
                    266:
1.17      afresh1   267: <li id="p016_perl">
1.29      bentley   268: <strong>016: SECURITY FIX: June 21, 2018</strong>
1.17      afresh1   269: &nbsp; <i>All architectures</i>
                    270: <br>
                    271: Perl's Archive::Tar module could be made to write files outside of
                    272: its working directory.
                    273: <br>
                    274: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/016_perl.patch.sig">
                    275: A source code patch exists which remedies this problem.</a>
                    276: <p>
                    277:
1.18      tj        278: <li id="p017_intelfpu">
1.29      bentley   279: <strong>017: SECURITY FIX: June 21, 2018</strong>
1.18      tj        280: &nbsp; <i>amd64</i>
                    281: <br>
                    282: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
                    283: so data (including AES keys) from previous contexts could be discovered
                    284: if using the lazy-save approach.
                    285: <br>
                    286: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/017_intelfpu.patch.sig">
                    287: A source code patch exists which remedies this problem.</a>
                    288: <p>
                    289:
1.19      tj        290: <li id="p018_execsize">
1.29      bentley   291: <strong>018: RELIABILITY FIX: July 25, 2018</strong>
1.19      tj        292: &nbsp; <i>All architectures</i>
                    293: <br>
                    294: A regular user could trigger a kernel panic by executing an invalid
                    295: ELF binary.
                    296: <br>
                    297: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/018_execsize.patch.sig">
                    298: A source code patch exists which remedies this problem.</a>
                    299: <p>
                    300:
1.20      tj        301: <li id="p019_amdlfence">
1.29      bentley   302: <strong>019: SECURITY FIX: July 31, 2018</strong>
1.20      tj        303: &nbsp; <i>amd64 and i386</i>
                    304: <br>
                    305: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
                    306: instruction against speculation.
                    307: <br>
                    308: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/019_amdlfence.patch.sig">
                    309: A source code patch exists which remedies this problem.</a>
                    310: <p>
                    311:
                    312: <li id="p020_ioport">
1.29      bentley   313: <strong>020: SECURITY FIX: July 31, 2018</strong>
1.20      tj        314: &nbsp; <i>i386</i>
                    315: <br>
                    316: IO port permissions were incorrectly restricted.
                    317: <br>
                    318: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/020_ioport.patch.sig">
                    319: A source code patch exists which remedies this problem.</a>
                    320: <p>
                    321:
1.21      tj        322: <li id="p021_fpuinit">
1.29      bentley   323: <strong>021: RELIABILITY FIX: August 4, 2018</strong>
1.21      tj        324: &nbsp; <i>amd64</i>
                    325: <br>
                    326: Incorrect initialization of the FPU caused floating point exceptions
                    327: when running on Xen.
                    328: <br>
                    329: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/021_fpuinit.patch.sig">
                    330: A source code patch exists which remedies this problem.</a>
                    331: <p>
                    332:
1.24      tj        333: <li id="p022_fpufork">
1.29      bentley   334: <strong>022: SECURITY FIX: August 24, 2018</strong>
1.24      tj        335: &nbsp; <i>amd64</i>
                    336: <br>
                    337: State from the FPU of one userland process could be exposed to other processes.
                    338: <br>
                    339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/022_fpufork.patch.sig">
                    340: A source code patch exists which remedies this problem.</a>
                    341: <p>
                    342:
                    343: <li id="p023_vmml1tf">
1.29      bentley   344: <strong>023: SECURITY FIX: August 24, 2018</strong>
1.24      tj        345: &nbsp; <i>amd64</i>
                    346: <br>
                    347: The Intel L1TF bug allows a vmm guest to read host memory.
                    348: Install the CPU firmware using fw_update(1), and apply this workaround.
                    349: <br>
                    350: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/023_vmml1tf.patch.sig">
                    351: A source code patch exists which remedies this problem.</a>
                    352: <p>
                    353:
1.25      tj        354: <li id="p024_ldtr">
1.29      bentley   355: <strong>024: SECURITY FIX: September 21, 2018</strong>
1.25      tj        356: &nbsp; <i>amd64</i>
                    357: <br>
                    358: On AMD CPUs, LDTR must be managed crossing between VMs.
                    359: <br>
                    360: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/024_ldtr.patch.sig">
                    361: A source code patch exists which remedies this problem.</a>
                    362: <p>
                    363:
1.1       deraadt   364: </ul>
                    365:
                    366: <hr>