Annotation of www/errata34.html, Revision 1.99
1.90 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.77 tj 5: <title>OpenBSD 3.4 Errata</title>
1.1 deraadt 6: <meta name="description" content="the OpenBSD CD errata page">
1.75 deraadt 7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.79 tb 9: <link rel="canonical" href="https://www.openbsd.org/errata34.html">
1.1 deraadt 10:
1.65 deraadt 11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
1.1 deraadt 15:
1.90 bentley 16: <h2 id=OpenBSD>
1.75 deraadt 17: <a href="index.html">
1.90 bentley 18: <i>Open</i><b>BSD</b></a>
19: 3.4 Errata
1.77 tj 20: </h2>
1.75 deraadt 21: <hr>
1.1 deraadt 22:
23: For errata on a certain release, click below:<br>
1.93 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>,
1.2 david 37: <a href="errata33.html">3.3</a>,
1.25 miod 38: <a href="errata35.html">3.5</a>,
1.33 deraadt 39: <a href="errata36.html">3.6</a>,
1.93 schwarze 40: <br>
1.58 deraadt 41: <a href="errata37.html">3.7</a>,
1.36 deraadt 42: <a href="errata38.html">3.8</a>,
1.37 deraadt 43: <a href="errata39.html">3.9</a>,
1.38 deraadt 44: <a href="errata40.html">4.0</a>,
1.41 merdely 45: <a href="errata41.html">4.1</a>,
1.42 deraadt 46: <a href="errata42.html">4.2</a>,
1.43 deraadt 47: <a href="errata43.html">4.3</a>,
1.45 deraadt 48: <a href="errata44.html">4.4</a>,
1.46 deraadt 49: <a href="errata45.html">4.5</a>,
1.47 deraadt 50: <a href="errata46.html">4.6</a>,
1.49 deraadt 51: <a href="errata47.html">4.7</a>,
1.50 miod 52: <a href="errata48.html">4.8</a>,
1.51 nick 53: <a href="errata49.html">4.9</a>,
1.52 sthen 54: <a href="errata50.html">5.0</a>,
1.53 deraadt 55: <a href="errata51.html">5.1</a>,
1.54 deraadt 56: <a href="errata52.html">5.2</a>,
1.93 schwarze 57: <br>
1.55 deraadt 58: <a href="errata53.html">5.3</a>,
1.56 deraadt 59: <a href="errata54.html">5.4</a>,
1.64 jsg 60: <a href="errata55.html">5.5</a>,
1.68 deraadt 61: <a href="errata56.html">5.6</a>,
1.71 deraadt 62: <a href="errata57.html">5.7</a>,
1.72 deraadt 63: <a href="errata58.html">5.8</a>,
1.78 deraadt 64: <a href="errata59.html">5.9</a>,
1.81 tj 65: <a href="errata60.html">6.0</a>,
1.86 deraadt 66: <a href="errata61.html">6.1</a>,
1.87 deraadt 67: <a href="errata62.html">6.2</a>,
1.88 deraadt 68: <a href="errata63.html">6.3</a>,
1.89 deraadt 69: <a href="errata64.html">6.4</a>,
1.92 deraadt 70: <a href="errata65.html">6.5</a>,
1.94 deraadt 71: <a href="errata66.html">6.6</a>,
1.95 deraadt 72: <a href="errata67.html">6.7</a>,
1.96 deraadt 73: <a href="errata68.html">6.8</a>,
1.97 tj 74: <br>
1.98 deraadt 75: <a href="errata69.html">6.9</a>,
1.99 ! deraadt 76: <a href="errata70.html">7.0</a>,
! 77: <a href="errata71.html">7.1</a>.
1.95 deraadt 78: <hr>
1.1 deraadt 79: <hr>
80:
1.59 deraadt 81: <p>
1.81 tj 82: Patches for the OpenBSD base system are distributed as unified diffs.
83: Each patch contains usage instructions.
84: All the following patches are also available in one
85: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4.tar.gz">tar.gz file</a>
86: for convenience.
1.1 deraadt 87:
1.59 deraadt 88: <p>
1.81 tj 89: Patches for supported releases are also incorporated into the
1.82 tj 90: <a href="stable.html">-stable branch</a>.
1.59 deraadt 91:
1.1 deraadt 92: <hr>
93:
94: <ul>
1.91 deraadt 95:
96: <li id="cd_booklet">
97: <strong>001: DOCUMENTATION FIX: November 1, 2003</strong>
98: <i>All architectures</i><br>
99: The CD insert documentation has an incorrect example for package installation.<br>
100: Where it is written:<p>
101: <b>
102: # pkg_add https://ftp.openbsd.org/pub/OpenBSD/3.4/packages/i386</b><p>
103: It should instead read:<p>
104: <b>
105: # pkg_add https://ftp.openbsd.org/pub/OpenBSD/3.4/packages/i386/</b><p>
106: The extra <b>/</b> at the end is important. We do not make
107: patch files available for things printed on paper.
108: <p>
109:
110: <li id="asn1">
111: <strong>002: SECURITY FIX: November 1, 2003</strong>
112: <i>All architectures</i><br>
113: The use of certain ASN.1 encodings or malformed public keys may allow an
114: attacker to mount a denial of service attack against applications linked with
115: <a href="https://man.openbsd.org/OpenBSD-3.4/ssl.3">ssl(3)</a>.
116: This does not affect OpenSSH.<br>
117: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/002_asn1.patch">
118: A source code patch exists which remedies this problem.</a>
119: <p>
120:
121: <li id="arp">
122: <strong>003: RELIABILITY FIX: November 1, 2003</strong>
1.62 deraadt 123: <i>All architectures</i><br>
1.91 deraadt 124: It is possible for a local user to cause a system panic by flooding it with spoofed ARP
125: requests.<br>
126: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/003_arp.patch">
1.59 deraadt 127: A source code patch exists which remedies this problem.</a>
1.31 markus 128: <p>
1.91 deraadt 129:
130: <li id="httpd">
131: <strong>004: RELIABILITY FIX: November 1, 2003</strong>
1.62 deraadt 132: <i>All architectures</i><br>
1.91 deraadt 133: A user with write permission to <code>httpd.conf</code> or a <code>.htaccess</code>
134: file can crash
135: <a href="https://man.openbsd.org/OpenBSD-3.4/httpd.8">httpd(8)</a>
136: or potentially run arbitrary code as the user <code>www</code> (although it
137: is believed that ProPolice will prevent code execution).
1.28 brad 138: <br>
1.91 deraadt 139: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/004_httpd.patch">
1.59 deraadt 140: A source code patch exists which remedies this problem.</a>
1.28 brad 141: <p>
1.91 deraadt 142:
143: <li id="exec">
144: <strong>005: RELIABILITY FIX: November 4, 2003</strong>
1.62 deraadt 145: <i>All architectures</i><br>
1.91 deraadt 146: It is possible for a local user to cause a system panic by executing a specially crafted binary with an invalid header.
1.26 brad 147: <br>
1.91 deraadt 148: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/005_exec.patch">
1.59 deraadt 149: A source code patch exists which remedies this problem.</a>
1.26 brad 150: <p>
1.91 deraadt 151:
152: <li id="ibcs2">
153: <strong>006: SECURITY FIX: November 17, 2003</strong>
154: <i>i386 only</i><br>
155: It may be possible for a local user to overrun the stack in
156: <a href="https://man.openbsd.org/OpenBSD-3.4/compat_ibcs2.8">compat_ibcs2(8)</a>.<br>
157: ProPolice catches this, turning a potential privilege escalation into a denial
158: of service. iBCS2 emulation does not need to be enabled via
159: <a href="https://man.openbsd.org/OpenBSD-3.4/sysctl.8">sysctl(8)</a>
160: for this to happen.
1.26 brad 161: <br>
1.91 deraadt 162: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/i386/006_ibcs2.patch">
1.59 deraadt 163: A source code patch exists which remedies this problem.</a>
1.26 brad 164: <p>
1.91 deraadt 165:
166: <li id="uvm">
167: <strong>007: RELIABILITY FIX: November 20, 2003</strong>
1.62 deraadt 168: <i>All architectures</i><br>
1.91 deraadt 169: It is possible for a local user to cause a crash via
170: <a href="https://man.openbsd.org/OpenBSD-3.4/sysctl.3">sysctl(3)</a> with certain arguments.
1.24 millert 171: <br>
1.91 deraadt 172: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/007_uvm.patch">
1.59 deraadt 173: A source code patch exists which remedies this problem.</a>
1.24 millert 174: <p>
1.91 deraadt 175:
176: <li id="sem">
177: <strong>008: RELIABILITY FIX: November 20, 2003</strong>
1.62 deraadt 178: <i>All architectures</i><br>
1.91 deraadt 179: An improper bounds check makes it possible for a local user to cause a crash
180: by passing the
181: <a href="https://man.openbsd.org/OpenBSD-3.4/semctl.2">semctl(2)</a> and
182: <a href="https://man.openbsd.org/OpenBSD-3.4/semop.2">semop(2)</a> functions
183: certain arguments.
1.23 brad 184: <br>
1.91 deraadt 185: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/008_sem.patch">
1.59 deraadt 186: A source code patch exists which remedies this problem.</a>
1.23 brad 187: <p>
1.91 deraadt 188:
189: <li id="isakmpd">
190: <strong>009: SECURITY FIX: January 13, 2004</strong>
1.62 deraadt 191: <i>All architectures</i><br>
1.91 deraadt 192: Several message handling flaws in
193: <a href="https://man.openbsd.org/OpenBSD-3.4/isakmpd.8">isakmpd(8)</a>
194: have been reported by Thomas Walpuski. These allow an attacker to delete arbitrary SAs. The patch also
195: includes a reliability fix for a filedescriptor leak that causes problems when a crypto card is
196: installed.
1.22 brad 197: <br>
1.91 deraadt 198: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/009_isakmpd.patch">
1.59 deraadt 199: A source code patch exists which remedies this problem.</a>
1.22 brad 200: <p>
201:
1.91 deraadt 202: <li id="sysvshm">
203: <strong>010: SECURITY FIX: February 5, 2004</strong>
1.62 deraadt 204: <i>All architectures</i><br>
1.91 deraadt 205: A reference counting bug exists in the
206: <a href="https://man.openbsd.org/OpenBSD-3.4/shmat.2">shmat(2)</a>
207: system call that could be used by an attacker to write to kernel memory
208: under certain circumstances.
1.19 brad 209: <br>
1.91 deraadt 210: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/010_sysvshm.patch">
1.59 deraadt 211: A source code patch exists which remedies this problem.</a>
1.19 brad 212: <p>
1.91 deraadt 213:
214: <li id="ip6">
215: <strong>011: SECURITY FIX: February 8, 2004</strong>
1.62 deraadt 216: <i>All architectures</i><br>
1.91 deraadt 217: An IPv6 MTU handling problem exists that could be used by an attacker
218: to cause a denial of service attack against hosts with reachable IPv6
219: TCP ports.
1.18 brad 220: <br>
1.91 deraadt 221: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/011_ip6.patch">
1.59 deraadt 222: A source code patch exists which remedies this problem.</a>
1.18 brad 223: <p>
1.91 deraadt 224:
225: <li id="font">
226: <strong>012: RELIABILITY FIX: February 14, 2004</strong>
1.62 deraadt 227: <i>All architectures</i><br>
1.91 deraadt 228: Several buffer overflows exist in the code parsing
229: font.aliases files in XFree86. Thanks to ProPolice, these cannot be
230: exploited to gain privileges, but they can cause the X server to abort.
1.17 brad 231: <br>
1.91 deraadt 232: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/012_font.patch">
1.59 deraadt 233: A source code patch exists which remedies this problem.</a>
1.17 brad 234: <p>
1.91 deraadt 235:
236: <li id="tcp">
237: <strong>013: RELIABILITY FIX: March 8, 2004</strong>
1.62 deraadt 238: <i>All architectures</i><br>
1.91 deraadt 239: OpenBSD's TCP/IP stack did not impose limits on how many out-of-order
240: TCP segments are queued in the system. An attacker could
241: send out-of-order TCP segments and trick the system into using all
242: available memory buffers.
1.15 brad 243: <br>
1.91 deraadt 244: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/013_tcp.patch">
1.59 deraadt 245: A source code patch exists which remedies this problem.</a>
1.15 brad 246: <p>
1.91 deraadt 247:
248: <li id="httpd2">
249: <strong>014: SECURITY FIX: March 13, 2004</strong>
1.62 deraadt 250: <i>All architectures</i><br>
1.91 deraadt 251: Due to a bug in the parsing of Allow/Deny rules for
252: <a href="https://man.openbsd.org/OpenBSD-3.4/httpd.8">httpd(8)'s</a>
253: access module, using IP addresses without a netmask on big endian 64-bit
254: platforms causes the rules to fail to match. This only affects sparc64.
1.14 brad 255: <br>
1.91 deraadt 256: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/014_httpd2.patch">
1.59 deraadt 257: A source code patch exists which remedies this problem.</a>
1.14 brad 258: <p>
1.91 deraadt 259:
260: <li id="isakmpd2">
261: <strong>015: RELIABILITY FIX: March 17, 2004</strong>
1.62 deraadt 262: <i>All architectures</i><br>
1.91 deraadt 263: Defects in the payload validation and processing functions of
264: <a href="https://man.openbsd.org/OpenBSD-3.4/isakmpd.8">isakmpd(8)</a>
265: have been discovered. An attacker could send malformed ISAKMP messages and
266: cause isakmpd to crash or to loop endlessly. This patch fixes these problems
267: and removes some memory leaks.
1.13 millert 268: <br>
1.91 deraadt 269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/015_isakmpd2.patch">
1.59 deraadt 270: A source code patch exists which remedies this problem.</a>
1.13 millert 271: <p>
1.91 deraadt 272:
273: <li id="openssl">
274: <strong>016: RELIABILITY FIX: March 17, 2004</strong>
1.62 deraadt 275: <i>All architectures</i><br>
1.91 deraadt 276: A missing check for a NULL-pointer dereference has been found in
277: <a href="https://man.openbsd.org/OpenBSD-3.4/ssl.3">ssl(3)</a>.
278: A remote attacker can use the bug to cause an OpenSSL application to crash;
279: this may lead to a denial of service.
1.10 beck 280: <br>
1.91 deraadt 281: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/016_openssl.patch">
1.59 deraadt 282: A source code patch exists which remedies this problem.</a>
1.10 beck 283: <p>
1.91 deraadt 284:
285: <li id="cvs">
286: <strong>017: SECURITY FIX: May 5, 2004</strong>
1.62 deraadt 287: <i>All architectures</i><br>
1.91 deraadt 288: Pathname validation problems have been found in
289: <a href="https://man.openbsd.org/OpenBSD-3.4/cvs.1">cvs(1)</a>,
290: allowing malicious clients to create files outside the repository, allowing
291: malicious servers to overwrite files outside the local CVS tree on
292: the client and allowing clients to check out files outside the CVS
293: repository.
1.9 otto 294: <br>
1.91 deraadt 295: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/017_cvs.patch">
1.59 deraadt 296: A source code patch exists which remedies this problem.</a>
1.9 otto 297: <p>
1.91 deraadt 298:
299: <li id="gdt">
300: <strong>018: RELIABILITY FIX: May 5, 2004</strong>
1.62 deraadt 301: <i>All architectures</i><br>
1.91 deraadt 302: Under load "recent model"
303: <a href="https://man.openbsd.org/OpenBSD-3.4/gdt.4">gdt(4)</a>
304: controllers will lock up.
1.7 tedu 305: <br>
1.91 deraadt 306: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/018_gdt.patch">
1.59 deraadt 307: A source code patch exists which remedies this problem.</a>
1.7 tedu 308: <p>
1.91 deraadt 309:
1.66 bentley 310: <li id="tcp2">
1.90 bentley 311: <strong>019: RELIABILITY FIX: May 6, 2004</strong>
1.62 deraadt 312: <i>All architectures</i><br>
1.6 brad 313: Reply to in-window SYN with a rate-limited ACK.
314: <br>
1.80 tb 315: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/019_tcp2.patch">
1.59 deraadt 316: A source code patch exists which remedies this problem.</a>
1.6 brad 317: <p>
1.91 deraadt 318:
319: <li id="procfs">
320: <strong>020: SECURITY FIX: May 13, 2004</strong>
1.62 deraadt 321: <i>All architectures</i><br>
1.91 deraadt 322: Check for integer overflow in procfs. Use of procfs is not recommended.
1.5 brad 323: <br>
1.91 deraadt 324: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/020_procfs.patch">
1.59 deraadt 325: A source code patch exists which remedies this problem.</a>
1.5 brad 326: <p>
1.91 deraadt 327:
328: <li id="cvs2">
329: <strong>021: SECURITY FIX: May 20, 2004</strong>
1.62 deraadt 330: <i>All architectures</i><br>
1.91 deraadt 331: A heap overflow in the
332: <a href="https://man.openbsd.org/OpenBSD-3.4/cvs.1">cvs(1)</a>
333: server has been discovered that can be exploited by clients sending
334: malformed requests, enabling these clients to run arbitrary code
335: with the same privileges as the CVS server program.
1.4 otto 336: <br>
1.91 deraadt 337: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/021_cvs2.patch">
1.59 deraadt 338: A source code patch exists which remedies this problem.</a>
1.4 otto 339: <p>
1.91 deraadt 340:
341: <li id="kerberos">
342: <strong>022: SECURITY FIX: May 30, 2004</strong>
1.62 deraadt 343: <i>All architectures</i><br>
1.91 deraadt 344: A flaw in the Kerberos V
345: <a href="https://man.openbsd.org/OpenBSD-3.4/kdc.8">kdc(8)</a>
346: server could result in the administrator of a Kerberos realm having
347: the ability to impersonate any principal in any other realm which
348: has established a cross-realm trust with their realm. The flaw is due to
349: inadequate checking of the "transited" field in a Kerberos request. For
350: more details see <a href="http://www.pdc.kth.se/heimdal/advisory/2004-04-01/">
351: Heimdal's announcement</a>.
1.1 deraadt 352: <br>
1.91 deraadt 353: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/022_kerberos.patch">
1.59 deraadt 354: A source code patch exists which remedies this problem.</a>
1.1 deraadt 355: <p>
1.91 deraadt 356:
357: <li id="cvs3">
358: <strong>023: SECURITY FIX: June 9, 2004</strong>
1.62 deraadt 359: <i>All architectures</i><br>
1.91 deraadt 360: Multiple remote vulnerabilities have been found in the
361: <a href="https://man.openbsd.org/OpenBSD-3.4/cvs.1">cvs(1)</a>
362: server that allow an attacker to crash the server or possibly execute arbitrary
363: code with the same privileges as the CVS server program.
1.1 deraadt 364: <br>
1.91 deraadt 365: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/023_cvs3.patch">
1.59 deraadt 366: A source code patch exists which remedies this problem.</a>
1.1 deraadt 367: <p>
1.91 deraadt 368:
369: <li id="isakmpd3">
370: <strong>024: SECURITY FIX: June 10, 2004</strong>
1.62 deraadt 371: <i>All architectures</i><br>
1.91 deraadt 372: As
373: <a href="http://seclists.org/lists/fulldisclosure/2004/Jun/0191.html">disclosed</a>
374: by Thomas Walpuski
375: <a href="https://man.openbsd.org/OpenBSD-3.4/isakmpd.8">isakmpd(8)</a>
376: is still vulnerable to unauthorized SA deletion. An attacker can delete IPsec
377: tunnels at will.
1.1 deraadt 378: <br>
1.91 deraadt 379: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/024_isakmpd3.patch">
1.59 deraadt 380: A source code patch exists which remedies this problem.</a>
1.1 deraadt 381: <p>
1.91 deraadt 382:
383: <li id="httpd3">
384: <strong>025: SECURITY FIX: June 12, 2004</strong>
1.62 deraadt 385: <i>All architectures</i><br>
1.91 deraadt 386: Multiple vulnerabilities have been found in
387: <a href="https://man.openbsd.org/OpenBSD-3.4/httpd.8">httpd(8)</a>
388: / mod_ssl.
389: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0020">CAN-2003-0020</a>,
390: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0987">CAN-2003-0987</a>,
391: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0488">CAN-2004-0488</a>,
392: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0492">CAN-2004-0492</a>.
1.1 deraadt 393: <br>
1.91 deraadt 394: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/025_httpd3.patch">
1.59 deraadt 395: A source code patch exists which remedies this problem.</a>
1.1 deraadt 396: <p>
1.91 deraadt 397:
398: <li id="rnd">
399: <strong>026: RELIABILITY FIX: Jul 25, 2004</strong>
1.62 deraadt 400: <i>All architectures</i><br>
1.91 deraadt 401: Under a certain network load the kernel can run out of stack space. This was
402: encountered in an environment using CARP on a VLAN interface. This issue initially
403: manifested itself as a FPU related crash on boot up.
1.1 deraadt 404: <br>
1.91 deraadt 405: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/026_rnd.patch">
1.59 deraadt 406: A source code patch exists which remedies this problem.</a>
1.1 deraadt 407: <p>
1.91 deraadt 408:
409: <li id="icmp">
410: <strong>027: RELIABILITY FIX: August 25, 2004</strong>
1.62 deraadt 411: <i>All architectures</i><br>
1.91 deraadt 412: Improved verification of ICMP errors in order to minimize the impact of ICMP attacks
413: against TCP.
414: <br>
415: <a href="http://www.gont.com.ar/drafts/icmp-attacks-against-tcp.html">http://www.gont.com.ar/drafts/icmp-attacks-against-tcp.html</a>
1.1 deraadt 416: <br>
1.91 deraadt 417: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/027_icmp.patch">
1.59 deraadt 418: A source code patch exists which remedies this problem.</a>
1.1 deraadt 419: <p>
1.91 deraadt 420:
421:
422:
423:
424:
425: <li id="pfkey">
426: <strong>035: SECURITY FIX: December 13, 2004</strong>
1.62 deraadt 427: <i>All architectures</i><br>
1.91 deraadt 428: On systems running
429: <a href="https://man.openbsd.org/OpenBSD-3.4/isakmpd.8">isakmpd(8)</a>
430: it is possible for a local user to cause kernel memory corruption
431: and system panic by setting
432: <a href="https://man.openbsd.org/OpenBSD-3.4/ipsec.4">ipsec(4)</a>
433: credentials on a socket.
1.1 deraadt 434: <br>
1.91 deraadt 435: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/035_pfkey.patch">
1.59 deraadt 436: A source code patch exists which remedies this problem.</a>
1.1 deraadt 437: <p>
1.91 deraadt 438:
439: <li id="lynx">
440: <strong>034: RELIABILITY FIX: November 10, 2004</strong>
1.62 deraadt 441: <i>All architectures</i><br>
1.91 deraadt 442: Due to a bug in
443: <a href="https://man.openbsd.org/OpenBSD-3.4/lynx.1">lynx(1)</a>
444: it is possible for pages such as
445: <a href="http://lcamtuf.coredump.cx/mangleme/gallery/lynx_die1.html">this</a>
446: to cause
447: <a href="https://man.openbsd.org/OpenBSD-3.4/lynx.1">lynx(1)</a>
448: to exhaust memory and then crash when parsing such pages.
1.1 deraadt 449: <br>
1.91 deraadt 450: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/034_lynx.patch">
1.59 deraadt 451: A source code patch exists which remedies this problem.</a>
1.1 deraadt 452: <p>
1.91 deraadt 453:
454: <li id="pppd">
455: <strong>033: RELIABILITY FIX: November 10, 2004</strong>
1.62 deraadt 456: <i>All architectures</i><br>
1.91 deraadt 457: <a href="https://man.openbsd.org/OpenBSD-3.4/pppd.8">pppd(8)</a>
458: contains a bug that allows an attacker to crash his own connection, but it cannot
459: be used to deny service to other users.
1.1 deraadt 460: <br>
1.91 deraadt 461: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/033_pppd.patch">
1.59 deraadt 462: A source code patch exists which remedies this problem.</a>
1.1 deraadt 463: <p>
1.91 deraadt 464:
465: <li id="bind">
466: <strong>032: RELIABILITY FIX: November 10, 2004</strong>
1.62 deraadt 467: <i>All architectures</i><br>
1.91 deraadt 468: BIND contains a bug which results in BIND trying to contact nameservers via IPv6, even in
469: cases where IPv6 connectivity is non-existent. This results in unnecessary timeouts and
470: thus slow DNS queries.
1.1 deraadt 471: <br>
1.91 deraadt 472: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/032_bind.patch">
1.59 deraadt 473: A source code patch exists which remedies this problem.</a>
1.1 deraadt 474: <p>
1.91 deraadt 475:
476: <li id="radius">
477: <strong>031: SECURITY FIX: September 20, 2004</strong>
478: <i>All architectures</i><br>
479: Eilko Bos reported that radius authentication, as implemented by
480: <a href="https://man.openbsd.org/OpenBSD-3.4/login_radius.8">login_radius(8)</a>,
481: was not checking the shared secret used for replies sent by the radius server.
482: This could allow an attacker to spoof a reply granting access to the
483: attacker. Note that OpenBSD does not ship with radius authentication enabled.
1.61 deraadt 484: <br>
1.91 deraadt 485: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/031_radius.patch">
1.61 deraadt 486: A source code patch exists which remedies this problem.</a>
487: <p>
1.91 deraadt 488:
489: <li id="xpm">
490: <strong>030: SECURITY FIX: September 16, 2004</strong>
1.62 deraadt 491: <i>All architectures</i><br>
1.91 deraadt 492: Chris Evans reported several flaws (stack and integer overflows) in the
493: <a href="http://www.inria.fr/koala/lehors/xpm.html">Xpm</a>
494: library code that parses image files
495: (<a href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0687">CAN-2004-0687</a>,
496: <a href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0688">CAN-2004-0688</a>).
497: Some of these would be exploitable when parsing malicious image files in
498: an application that handles XPM images, if they could escape ProPolice.
1.1 deraadt 499: <br>
1.91 deraadt 500: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/030_xpm.patch">
1.59 deraadt 501: A source code patch exists which remedies this problem.</a>
1.1 deraadt 502: <p>
1.91 deraadt 503:
504: <li id="httpd4">
505: <strong>029: SECURITY FIX: September 10, 2004</strong>
1.62 deraadt 506: <i>All architectures</i><br>
1.84 tb 507: <a href="https://man.openbsd.org/OpenBSD-3.4/httpd.8">httpd(8)</a>
1.91 deraadt 508: 's mod_rewrite module can be made to write one zero byte in an arbitrary memory
509: position outside of a char array, causing a DoS or possibly buffer overflows.
510: This would require enabling dbm for mod_rewrite and making use of a malicious
511: dbm file.
1.1 deraadt 512: <br>
1.91 deraadt 513: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/029_httpd4.patch">
1.59 deraadt 514: A source code patch exists which remedies this problem.</a>
1.1 deraadt 515: <p>
1.91 deraadt 516:
517: <li id="bridge">
518: <strong>028: RELIABILITY FIX: August 26, 2004</strong>
1.62 deraadt 519: <i>All architectures</i><br>
1.91 deraadt 520: As
521: <a href="https://marc.info/?l=bugtraq&m=109345131508824&w=2">reported</a>
522: by Vafa Izadinia
523: <a href="https://man.openbsd.org/OpenBSD-3.4/bridge.4">bridge(4)</a>
524: with IPsec processing enabled can be crashed remotely by a single ICMP echo traversing the bridge.
525: <br>
526: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/3.4/common/028_bridge.patch">
1.59 deraadt 527: A source code patch exists which remedies this problem.</a>
1.1 deraadt 528: <p>
1.78 deraadt 529:
1.1 deraadt 530: </ul>
531:
1.67 tedu 532: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata34.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www