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

Annotation of www/errata64.html, Revision 1.14

1.1       deraadt     1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
                      2: <html>
                      3: <head>
                      4: <title>OpenBSD 6.4 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">
1.7       deraadt     9: <link rel="canonical" href="https://www.openbsd.org/errata64.html">
1.1       deraadt    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.4 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: <a href="errata62.html">6.2</a>,
1.2       tb         70: <a href="errata63.html">6.3</a>.
1.1       deraadt    71: <hr>
                     72:
                     73: <p>
                     74: Patches for the OpenBSD base system are distributed as unified diffs.
                     75: Each patch is cryptographically signed with the
1.3       tb         76: <a href="https://man.openbsd.org/OpenBSD-6.4/signify.1">signify(1)</a> tool and contains
1.1       deraadt    77: usage instructions.
                     78: All the following patches are also available in one
                     79: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4.tar.gz">tar.gz file</a>
                     80: for convenience.
                     81:
                     82: <p>
                     83: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
                     84: utility can be used to apply binary updates on the following architectures:
                     85: amd64, i386, arm64.
                     86:
                     87: <p>
                     88: Patches for supported releases are also incorporated into the
                     89: <a href="stable.html">-stable branch</a>, which is maintained for one year
                     90: after release.
                     91:
                     92: <hr>
                     93:
                     94: <ul>
                     95:
1.4       tj         96: <li id="p001_xserver">
                     97: <font color="#009000">
                     98: <strong>001: SECURITY FIX: October 25, 2018</strong></font>
                     99: &nbsp; <i>All architectures</i>
                    100: <br>
                    101: The Xorg X server incorrectly validates certain options, allowing arbitrary
                    102: files to be overwritten.
                    103: As an immediate (temporary) workaround, the Xorg binary can be disabled
                    104: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
                    105: <br>
                    106: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
                    107: A source code patch exists which remedies this problem.</a>
                    108: <p>
1.1       deraadt   109:
1.5       tj        110: <li id="p002_syspatch">
                    111: <font color="#009000">
                    112: <strong>002: RELIABILITY FIX: November 2, 2018</strong></font>
                    113: &nbsp; <i>i386, amd64, arm64</i>
                    114: <br>
                    115: The syspatch utility incorrectly handles symbolic links.
                    116: <br>
                    117: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
                    118: A source code patch exists which remedies this problem.</a>
                    119: <p>
                    120:
1.6       tj        121: <li id="p003_portsmash">
                    122: <font color="#009000">
                    123: <strong>003: SECURITY FIX: November 17, 2018</strong></font>
                    124: &nbsp; <i>All architectures</i>
                    125: <br>
                    126: The portsmash vulnerability allows exfiltration of elliptic curve keys.
                    127: <br>
                    128: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
                    129: A source code patch exists which remedies this problem.</a>
                    130: <p>
                    131:
                    132: <li id="p004_lockf">
                    133: <font color="#009000">
                    134: <strong>004: RELIABILITY FIX: November 17, 2018</strong></font>
                    135: &nbsp; <i>All architectures</i>
                    136: <br>
                    137: A recent change to POSIX file locks could cause incorrect results
                    138: during lock acquisition.
                    139: <br>
                    140: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
                    141: A source code patch exists which remedies this problem.</a>
                    142: <p>
                    143:
1.8       tj        144: <li id="p005_perl">
                    145: <font color="#009000">
                    146: <strong>005: SECURITY FIX: November 29, 2018</strong></font>
                    147: &nbsp; <i>All architectures</i>
                    148: <br>
                    149: Various overflows exist in perl.
                    150: <br>
                    151: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
                    152: A source code patch exists which remedies this problem.</a>
                    153: <p>
                    154:
                    155: <li id="p006_uipc">
                    156: <font color="#009000">
                    157: <strong>006: RELIABILITY FIX: November 29, 2018</strong></font>
                    158: &nbsp; <i>All architectures</i>
                    159: <br>
                    160: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
                    161: attempt excessive memory allocations leading to a crash.
                    162: <br>
                    163: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
                    164: A source code patch exists which remedies this problem.</a>
                    165: <p>
                    166:
                    167: <li id="p007_smtpd">
                    168: <font color="#009000">
                    169: <strong>007: RELIABILITY FIX: November 29, 2018</strong></font>
                    170: &nbsp; <i>All architectures</i>
                    171: <br>
                    172: The mail.mda and mail.lmtp delivery agents were not reporting temporary
                    173: failures correctly, causing smtpd to bounce messages in some cases where
                    174: it should have retried them.
                    175: <br>
                    176: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
                    177: A source code patch exists which remedies this problem.</a>
                    178: <p>
                    179:
                    180: <li id="p008_qcow2">
                    181: <font color="#009000">
                    182: <strong>008: RELIABILITY FIX: November 29, 2018</strong></font>
                    183: &nbsp; <i>amd64 and i386</i>
                    184: <br>
                    185: Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
                    186: <br>
                    187: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
                    188: A source code patch exists which remedies this problem.</a>
                    189: <p>
                    190:
1.9       tj        191: <li id="p009_recvwait">
                    192: <font color="#009000">
                    193: <strong>009: RELIABILITY FIX: December 20, 2018</strong></font>
                    194: &nbsp; <i>All architectures</i>
                    195: <br>
                    196: While recv(2) with the MSG_WAITALL flag was receiving control
                    197: messages from a socket, the kernel could panic.
                    198: <br>
                    199: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
                    200: A source code patch exists which remedies this problem.</a>
                    201: <p>
                    202:
1.10      tj        203: <li id="p010_pcbopts">
                    204: <font color="#009000">
                    205: <strong>010: SECURITY FIX: December 22, 2018</strong></font>
                    206: &nbsp; <i>All architectures</i>
                    207: <br>
                    208: The setsockopt(2) system call could overflow mbuf cluster kernel
                    209: memory by 4 bytes.
                    210: <br>
                    211: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
                    212: A source code patch exists which remedies this problem.</a>
                    213: <p>
                    214:
1.11      tj        215: <li id="p011_mincore">
                    216: <font color="#009000">
                    217: <strong>011: SECURITY FIX: January 27, 2019</strong></font>
                    218: &nbsp; <i>All architectures</i>
                    219: <br>
                    220: The mincore() system call can be used to observe memory access patterns
                    221: of other processes.
                    222: <br>
                    223: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
                    224: A source code patch exists which remedies this problem.</a>
                    225: <p>
                    226:
                    227: <li id="p012_nfs">
                    228: <font color="#009000">
                    229: <strong>012: RELIABILITY FIX: January 27, 2019</strong></font>
                    230: &nbsp; <i>All architectures</i>
                    231: <br>
                    232: Missing length checks in the NFS server and client can lead to crashes
                    233: and other errors.
                    234: <br>
                    235: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
                    236: A source code patch exists which remedies this problem.</a>
                    237: <p>
                    238:
                    239: <li id="p013_unveil">
                    240: <font color="#009000">
                    241: <strong>013: SECURITY FIX: January 27, 2019</strong></font>
                    242: &nbsp; <i>All architectures</i>
                    243: <br>
                    244: The unveil() system call can leak memory.
                    245: <br>
                    246: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
                    247: A source code patch exists which remedies this problem.</a>
                    248: <p>
                    249:
1.12      tj        250: <li id="p014_pf6frag">
                    251: <font color="#009000">
                    252: <strong>014: SECURITY FIX: March 1, 2019</strong></font>
                    253: &nbsp; <i>All architectures</i>
                    254: <br>
                    255: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
                    256: <br>
                    257: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
                    258: A source code patch exists which remedies this problem.</a>
                    259: <p>
                    260:
1.13      tj        261: <li id="p015_pficmp">
                    262: <font color="#009000">
                    263: <strong>015: SECURITY FIX: March 22, 2019</strong></font>
                    264: &nbsp; <i>All architectures</i>
                    265: <br>
                    266: A state in pf could pass ICMP packets to a destination IP address
                    267: that did not match the state.
                    268: <br>
                    269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
                    270: A source code patch exists which remedies this problem.</a>
                    271: <p>
                    272:
1.14    ! tj        273: <li id="p016_vmmints">
        !           274: <font color="#009000">
        !           275: <strong>016: SECURITY FIX: March 27, 2019</strong></font>
        !           276: &nbsp; <i>amd64 and i386</i>
        !           277: <br>
        !           278: GDT and IDT limits were improperly restored during VMM context switches.
        !           279: <br>
        !           280: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
        !           281: A source code patch exists which remedies this problem.</a>
        !           282: <p>
        !           283:
1.1       deraadt   284: </ul>
                    285:
                    286: <hr>
                    287:
                    288: </body>
                    289: </html>