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

Annotation of www/errata64.html, Revision 1.30

1.19      bentley     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
1.1       deraadt     5: <title>OpenBSD 6.4 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">
1.7       deraadt     9: <link rel="canonical" href="https://www.openbsd.org/errata64.html">
1.1       deraadt    10:
                     11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
1.19      bentley    16: <h2 id=OpenBSD>
1.1       deraadt    17: <a href="index.html">
1.19      bentley    18: <i>Open</i><b>BSD</b></a>
                     19: 6.4 Errata
1.1       deraadt    20: </h2>
                     21: <hr>
                     22:
                     23: For errata on a certain release, click below:<br>
1.30    ! 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.30    ! 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.30    ! 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>,
                     67: <a href="errata61.html">6.1</a>,
                     68: <a href="errata62.html">6.2</a>,
1.15      deraadt    69: <a href="errata63.html">6.3</a>,
1.27      deraadt    70: <a href="errata65.html">6.5</a>,
                     71: <a href="errata66.html">6.6</a>.
1.1       deraadt    72: <hr>
                     73:
                     74: <p>
                     75: Patches for the OpenBSD base system are distributed as unified diffs.
                     76: Each patch is cryptographically signed with the
1.3       tb         77: <a href="https://man.openbsd.org/OpenBSD-6.4/signify.1">signify(1)</a> tool and contains
1.1       deraadt    78: usage instructions.
                     79: All the following patches are also available in one
                     80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4.tar.gz">tar.gz file</a>
                     81: for convenience.
                     82:
                     83: <p>
                     84: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
                     85: utility can be used to apply binary updates on the following architectures:
                     86: amd64, i386, arm64.
                     87:
                     88: <p>
                     89: Patches for supported releases are also incorporated into the
1.29      tj         90: <a href="stable.html">-stable branch</a>.
1.1       deraadt    91:
                     92: <hr>
                     93:
                     94: <ul>
                     95:
1.4       tj         96: <li id="p001_xserver">
1.19      bentley    97: <strong>001: SECURITY FIX: October 25, 2018</strong>
1.4       tj         98: &nbsp; <i>All architectures</i>
                     99: <br>
                    100: The Xorg X server incorrectly validates certain options, allowing arbitrary
                    101: files to be overwritten.
                    102: As an immediate (temporary) workaround, the Xorg binary can be disabled
                    103: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
                    104: <br>
                    105: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
                    106: A source code patch exists which remedies this problem.</a>
                    107: <p>
1.1       deraadt   108:
1.5       tj        109: <li id="p002_syspatch">
1.19      bentley   110: <strong>002: RELIABILITY FIX: November 2, 2018</strong>
1.5       tj        111: &nbsp; <i>i386, amd64, arm64</i>
                    112: <br>
                    113: The syspatch utility incorrectly handles symbolic links.
                    114: <br>
                    115: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
                    116: A source code patch exists which remedies this problem.</a>
                    117: <p>
                    118:
1.6       tj        119: <li id="p003_portsmash">
1.19      bentley   120: <strong>003: SECURITY FIX: November 17, 2018</strong>
1.6       tj        121: &nbsp; <i>All architectures</i>
                    122: <br>
                    123: The portsmash vulnerability allows exfiltration of elliptic curve keys.
                    124: <br>
                    125: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
                    126: A source code patch exists which remedies this problem.</a>
                    127: <p>
                    128:
                    129: <li id="p004_lockf">
1.19      bentley   130: <strong>004: RELIABILITY FIX: November 17, 2018</strong>
1.6       tj        131: &nbsp; <i>All architectures</i>
                    132: <br>
                    133: A recent change to POSIX file locks could cause incorrect results
                    134: during lock acquisition.
                    135: <br>
                    136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
                    137: A source code patch exists which remedies this problem.</a>
                    138: <p>
                    139:
1.8       tj        140: <li id="p005_perl">
1.19      bentley   141: <strong>005: SECURITY FIX: November 29, 2018</strong>
1.8       tj        142: &nbsp; <i>All architectures</i>
                    143: <br>
                    144: Various overflows exist in perl.
                    145: <br>
                    146: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
                    147: A source code patch exists which remedies this problem.</a>
                    148: <p>
                    149:
                    150: <li id="p006_uipc">
1.19      bentley   151: <strong>006: RELIABILITY FIX: November 29, 2018</strong>
1.8       tj        152: &nbsp; <i>All architectures</i>
                    153: <br>
                    154: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
                    155: attempt excessive memory allocations leading to a crash.
                    156: <br>
                    157: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
                    158: A source code patch exists which remedies this problem.</a>
                    159: <p>
                    160:
                    161: <li id="p007_smtpd">
1.19      bentley   162: <strong>007: RELIABILITY FIX: November 29, 2018</strong>
1.8       tj        163: &nbsp; <i>All architectures</i>
                    164: <br>
                    165: The mail.mda and mail.lmtp delivery agents were not reporting temporary
                    166: failures correctly, causing smtpd to bounce messages in some cases where
                    167: it should have retried them.
                    168: <br>
                    169: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
                    170: A source code patch exists which remedies this problem.</a>
                    171: <p>
                    172:
                    173: <li id="p008_qcow2">
1.19      bentley   174: <strong>008: RELIABILITY FIX: November 29, 2018</strong>
1.8       tj        175: &nbsp; <i>amd64 and i386</i>
                    176: <br>
                    177: Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
                    178: <br>
                    179: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
                    180: A source code patch exists which remedies this problem.</a>
                    181: <p>
                    182:
1.9       tj        183: <li id="p009_recvwait">
1.19      bentley   184: <strong>009: RELIABILITY FIX: December 20, 2018</strong>
1.9       tj        185: &nbsp; <i>All architectures</i>
                    186: <br>
                    187: While recv(2) with the MSG_WAITALL flag was receiving control
                    188: messages from a socket, the kernel could panic.
                    189: <br>
                    190: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
                    191: A source code patch exists which remedies this problem.</a>
                    192: <p>
                    193:
1.10      tj        194: <li id="p010_pcbopts">
1.19      bentley   195: <strong>010: SECURITY FIX: December 22, 2018</strong>
1.10      tj        196: &nbsp; <i>All architectures</i>
                    197: <br>
                    198: The setsockopt(2) system call could overflow mbuf cluster kernel
                    199: memory by 4 bytes.
                    200: <br>
                    201: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
                    202: A source code patch exists which remedies this problem.</a>
                    203: <p>
                    204:
1.11      tj        205: <li id="p011_mincore">
1.19      bentley   206: <strong>011: SECURITY FIX: January 27, 2019</strong>
1.11      tj        207: &nbsp; <i>All architectures</i>
                    208: <br>
                    209: The mincore() system call can be used to observe memory access patterns
                    210: of other processes.
                    211: <br>
                    212: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
                    213: A source code patch exists which remedies this problem.</a>
                    214: <p>
                    215:
                    216: <li id="p012_nfs">
1.19      bentley   217: <strong>012: RELIABILITY FIX: January 27, 2019</strong>
1.11      tj        218: &nbsp; <i>All architectures</i>
                    219: <br>
                    220: Missing length checks in the NFS server and client can lead to crashes
                    221: and other errors.
                    222: <br>
                    223: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
                    224: A source code patch exists which remedies this problem.</a>
                    225: <p>
                    226:
                    227: <li id="p013_unveil">
1.19      bentley   228: <strong>013: SECURITY FIX: January 27, 2019</strong>
1.11      tj        229: &nbsp; <i>All architectures</i>
                    230: <br>
                    231: The unveil() system call can leak memory.
                    232: <br>
                    233: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
                    234: A source code patch exists which remedies this problem.</a>
                    235: <p>
                    236:
1.12      tj        237: <li id="p014_pf6frag">
1.19      bentley   238: <strong>014: SECURITY FIX: March 1, 2019</strong>
1.12      tj        239: &nbsp; <i>All architectures</i>
                    240: <br>
                    241: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
                    242: <br>
                    243: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
                    244: A source code patch exists which remedies this problem.</a>
                    245: <p>
                    246:
1.13      tj        247: <li id="p015_pficmp">
1.19      bentley   248: <strong>015: SECURITY FIX: March 22, 2019</strong>
1.13      tj        249: &nbsp; <i>All architectures</i>
                    250: <br>
                    251: A state in pf could pass ICMP packets to a destination IP address
                    252: that did not match the state.
                    253: <br>
                    254: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
                    255: A source code patch exists which remedies this problem.</a>
                    256: <p>
                    257:
1.14      tj        258: <li id="p016_vmmints">
1.19      bentley   259: <strong>016: SECURITY FIX: March 27, 2019</strong>
1.14      tj        260: &nbsp; <i>amd64 and i386</i>
                    261: <br>
                    262: GDT and IDT limits were improperly restored during VMM context switches.
                    263: <br>
                    264: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
                    265: A source code patch exists which remedies this problem.</a>
                    266: <p>
                    267:
1.16      tj        268: <li id="p017_rip6cksum">
1.19      bentley   269: <strong>017: RELIABILITY FIX: May 3, 2019</strong>
1.16      tj        270: &nbsp; <i>All architectures</i>
                    271: <br>
                    272: If a userland program sets the IPv6 checksum offset on a raw socket,
                    273: an incoming packet could crash the kernel.  ospf6d is such a program.
                    274: <br>
                    275: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/017_rip6cksum.patch.sig">
                    276: A source code patch exists which remedies this problem.</a>
                    277: <p>
                    278:
1.20      tj        279: <li id="p018_mds">
                    280: <strong>018: SECURITY FIX: May 29, 2019</strong>
                    281: &nbsp; <i>amd64</i>
                    282: <br>
                    283: Intel CPUs have a cross privilege side-channel attack (MDS).
                    284: <br>
                    285: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/018_mds.patch.sig">
                    286: A source code patch exists which remedies this problem.</a>
                    287: <p>
                    288:
1.21      tj        289: <li id="p019_tcpsack">
                    290: <strong>019: RELIABILITY FIX: July 25, 2019</strong>
1.22      tj        291: &nbsp; <i>All architectures</i>
1.21      tj        292: <br>
                    293: By creating long chains of TCP SACK holes, an attacker could possibly
                    294: slow down the system temporarily.
                    295: <br>
                    296: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/019_tcpsack.patch.sig">
                    297: A source code patch exists which remedies this problem.</a>
                    298: <p>
                    299:
1.23      tj        300: <li id="p020_smtpd">
                    301: <strong>020: RELIABILITY FIX: August 2, 2019</strong>
                    302: &nbsp; <i>All architectures</i>
                    303: <br>
                    304: smtpd can crash on excessively large input, causing a denial of service.
                    305: <br>
                    306: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/020_smtpd.patch.sig">
                    307: A source code patch exists which remedies this problem.</a>
                    308: <p>
                    309:
1.24      tj        310: <li id="p021_swapgs">
                    311: <strong>021: SECURITY FIX: August 9, 2019</strong>
                    312: &nbsp; <i>amd64</i>
                    313: <br>
                    314: Intel CPUs have another cross privilege side-channel attack. (SWAPGS)
                    315: <br>
                    316: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/021_swapgs.patch.sig">
                    317: A source code patch exists which remedies this problem.</a>
                    318: <p>
                    319:
1.25      tj        320: <li id="p022_resume">
                    321: <strong>022: RELIABILITY FIX: September 2, 2019</strong>
                    322: &nbsp; <i>amd64</i>
                    323: <br>
                    324: Resume forgot to restore MSR/PAT configuration.
                    325: <br>
                    326: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/022_resume.patch.sig">
                    327: A source code patch exists which remedies this problem.</a>
                    328: <p>
                    329:
                    330: <li id="p023_frag6ecn">
                    331: <strong>023: RELIABILITY FIX: September 2, 2019</strong>
                    332: &nbsp; <i>All architectures</i>
                    333: <br>
                    334: When processing ECN bits on incoming IPv6 fragments, the kernel
                    335: could crash.  Per default pf fragment reassemble prevents the crash.
                    336: <br>
                    337: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/023_frag6ecn.patch.sig">
                    338: A source code patch exists which remedies this problem.</a>
                    339: <p>
                    340:
1.26      tj        341: <li id="p024_expat">
                    342: <strong>024: SECURITY FIX: September 14, 2019</strong>
                    343: &nbsp; <i>All architectures</i>
                    344: <br>
                    345: Libexpat 2.2.6 was affected by the heap overflow CVE-2019-15903.
                    346: <br>
                    347: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/024_expat.patch.sig">
                    348: A source code patch exists which remedies this problem.</a>
                    349: <p>
                    350:
1.28      tj        351: <li id="p025_unbound">
                    352: <strong>025: RELIABILITY FIX: October 5, 2019</strong>
                    353: &nbsp; <i>All architectures</i>
                    354: <br>
                    355: Specially crafted queries may crash unwind and unbound.
                    356: <br>
                    357: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/025_unbound.patch.sig">
                    358: A source code patch exists which remedies this problem.</a>
                    359: <p>
                    360:
                    361: <li id="p026_dhcpd">
                    362: <strong>026: SECURITY FIX: October 5, 2019</strong>
                    363: &nbsp; <i>All architectures</i>
                    364: <br>
                    365: dhcpd leaks 4 bytes of stack to the network.
                    366: <br>
                    367: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/026_dhcpd.patch.sig">
                    368: A source code patch exists which remedies this problem.</a>
                    369: <p>
                    370:
1.1       deraadt   371: </ul>
                    372:
                    373: <hr>