OpenBSD 4.8 发布08,09,10号补丁
发表于 : 2011-02-18 11:20
如何应用补丁请参阅:http://gobsd.org/showthread.php?t=2175http://www.gobsd.org/threads/2362
You can also fetch a tar.gz file containing all the following patches. This file is updated once a day.
The patches below are available in CVS via the OPENBSD_4_8 patch branch.
For more detailed information on how to install patches to OpenBSD, please consult the OpenBSD FAQ.
010: RELIABILITY FIX: February 16, 2011 All architectures
The sis(4) driver may hand over stale ring descriptors to the hardware if the compiler decides to re-order stores or if the hardware does store-reordering.
A source code patch exists which remedies this problem.
009: SECURITY FIX: February 16, 2011 Little-endian architectures
PF rules specifying address ranges (e.g. "10.1.1.1 - 10.1.1.5") were not correctly handled on little-endian systems (alpha, amd64, arm, i386, mips64el, vax). Other address types (bare addresses "10.1.1.1" and prefixes "10.1.1.1/30") are not affected.
A source code patch exists which remedies this problem.
008: SECURITY FIX: February 11, 2011 All architectures
An incorrectly formatted ClientHello handshake message could cause OpenSSL to parse past the end of the message. An attacker could use this flaw to trigger an invalid memory access, causing a crash of an application linked to OpenSSL. As well, certain applications may expose the contents of parsed OCSP extensions, specifically the OCSP nonce extension.
Applications are only affected if they act as a server and call SSL_CTX_set_tlsext_status_cb on the server's SSL_CTX. It is believed that nothing in the base OS uses this. Apache httpd started using this in v2.3.3; this is newer than the version in ports.
A source code patch exists which remedies this problem.
007: RELIABILITY FIX: January 13, 2011 All architectures
sp_protocol in RTM_DELETE messages could contain garbage values leading to routing socket users that restrict the AF (such as ospfd) not seeing any of the RTM_DELETE messages.
A source code patch exists which remedies this problem.
006: RELIABILITY FIX: December 17, 2010 All architectures
Bring CBC oracle attack countermeasures to hardware crypto accelerator land. This fixes aes-ni, via xcrypt and various drivers (glxsb(4), hifn(4), safe(4) and ubsec(4)).
A source code patch exists which remedies this problem.
005: SECURITY FIX: December 17, 2010 All architectures
Insufficent initialization of the pf rule structure in the ioctl handler may allow userland to modify kernel memory. By default root privileges are needed to add or modify pf rules.
A source code patch exists which remedies this problem.
004: RELIABILITY FIX: November 17, 2010 All architectures
Fix a flaw in the OpenSSL TLS server extension code parsing which could lead to a buffer overflow. This affects OpenSSL based TLS servers which are multi-threaded and use OpenSSL's internal caching mechanism. Servers that are multi-process and/or disable internal session caching are not affected.
A source code patch exists which remedies this problem.
003: RELIABILITY FIX: November 16, 2010 All architectures
The vr(4) driver may hand over stale ring descriptors to the hardware if the compiler decides to re-order stores or if the hardware does store-reordering.
A source code patch exists which remedies this problem.
002: RELIABILITY FIX: November 16, 2010 All architectures
Certain PCI based hardware may improperly announce their Base Address Registers as prefetchable even though they are not. This may cause unpredictable effects due to wrongly mapped memory.
A source code patch exists which remedies this problem.
001: RELIABILITY FIX: November 16, 2010 All architectures
Uninitialized memory may force the RDE into route-collector mode on startup and may prevent bgpd from updating or announcing any routes.
A source code patch exists which remedies this problem.