VARIoT IoT vulnerabilities database
| VAR-201801-1836 | No CVE | D-Link DSL-6850U Router Remote Command Execution Vulnerability |
CVSS V2: 10.0 CVSS V3: - Severity: HIGH |
D-LinkDSL-6850U is a wireless router product of D-Link. D-LinkDSL-6850U Router Remote Command Execution Vulnerability. Since the router has the remote web management service enabled by default, the service has the default credentials support:support and cannot be disabled. The attacker can log in to the router's web management interface through the default credentials, and then manually open the Wan port telnet service that is turned off by default. After logging in to the telnet service, you can use the && or || command sandbox escape to get full shell permissions.
| VAR-201801-0589 | CVE-2017-16753 | Advantech WebAccess Input validation vulnerability |
CVSS V2: 5.0 CVSS V3: 7.5 Severity: HIGH |
An Improper Input Validation issue was discovered in Advantech WebAccess versions prior to 8.3. WebAccess allows some inputs that may cause the program to crash. Advantech WebAccess Contains an input validation vulnerability.Service operation interruption (DoS) There is a possibility of being put into a state. Advantech WebAccess is a suite of browser-based HMI/SCADA software from Advantech. The software supports dynamic graphical display and real-time data control, and provides the ability to remotely control and manage automation equipment. The vulnerability is caused by a failure to properly validate WebAccess input. Advantech WebAccess is prone to the following security vulnerabilities:
1. Multiple denial-of-service vulnerabilities
2. Multiple stack-based buffer-overflow vulnerabilities
3. A directory-traversal vulnerability
4. An SQL-injection vulnerability
5. Multiple denial-of-service vulnerabilities
An attacker can exploit these issues to execute arbitrary code in the context of the application, or modify data, or exploit latent vulnerabilities in the underlying database,perform certain unauthorized actions, gain unauthorized access and obtain sensitive information
| VAR-201801-1712 | CVE-2017-5753 | CPU hardware utilizing speculative execution may be vulnerable to cache side-channel attacks |
CVSS V2: 4.7 CVSS V3: 5.6 Severity: MEDIUM |
Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. Two vulnerabilities are identified, known as "Variant 3a" and "Variant 4". CPUhardware is a set of firmware that runs in the CPU (Central Processing Unit) for managing and controlling the CPU. The Meltdown vulnerability exists in the CPU processor core, which \"melts\" the security boundary implemented by hardware, allowing low-privileged user-level applications to \"cross-border\" access to system-level memory, causing data leakage. The following products and versions are affected: ARM Cortex-R7; Cortex-R8; Cortex-A8; Cortex-A9; Cortex-A12; Xeon CPU E5-1650 v3, v2, v4; Xeon E3-1265l v2, v3, v4 ; Xeon E3-1245 v2, v3, v5, v6 versions; Xeon X7542, etc. Relevant releases/architectures:
Image Updates for RHV-H - noarch
3. These
packages include redhat-release-virtualization-host, ovirt-node, and
rhev-hypervisor. RHVH features a Cockpit user interface for
monitoring the host's resources and performing administrative tasks. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
APPLE-SA-2018-1-8-3 Safari 11.0.2
Safari 11.0.2 is now available and and addresses the following:
Available for: OS X El Capitan 10.11.6 and macOS Sierra 10.12.6
Description: Safari 11.0.2 includes security improvements to mitigate
the effects of Spectre (CVE- 2017-5753 and CVE-2017-5715).
We would like to acknowledge Jann Horn of Google Project Zero; and
Paul Kocher in collaboration with Daniel Genkin of University of
Pennsylvania and University of Maryland, Daniel Gruss of Graz
University of Technology, Werner Haas of Cyberus Technology,
Mike Hamburg of Rambus (Cryptography Research Division),
Moritz Lipp of Graz University of Technology, Stefan Mangard of
Graz University of Technology, Thomas Prescher of Cyberus Technology,
Michael Schwarz of Graz University of Technology, and Yuval Yarom of
University of Adelaide and Data61 for their assistance.
Installation note:
Safari 11.0.2 may be obtained from the Mac App Store.
Bug Fix(es):
* Previously, the page table isolation feature was able to modify the
kernel Page Global Directory (PGD) entries with the _NX bit even for CPUs
without the capability to use the "no execute" (NX) bit technology.
Consequently, the page tables got corrupted, and the kernel panicked at the
first page-fault occurrence. This update adds the check of CPU capabilities
before modifying kernel PGD entries with _NX. As a result, the operating
system no longer panics on boot due to corrupted page tables under the
described circumstances. (BZ#1538169)
* When booting the operating system with the Kernel Page Table Isolation
option enabled, the HPET VSYSCALL shadow mapping was not placed correctly.
Consequently, the High Precision Event Timer (HPET) feature was not
available early enough, and warnings on boot time occurred. This update
fixes the placement of HPET VSYSCALL, and the warnings on boot time due to
this behavior no longer occur. (BZ#1541281)
* Previously, the routine preparing the kexec crashkernel area did not
properly clear the page allocated to be kexec's Page Global Directory
(PGD). Consequently, the page table isolation shadow mapping routines
failed with a warning message when setting up page table entries. With this
update, the underlying source code has been fixed to clear the kexec PGD
allocated page before setting up its page table entries. As a result,
warnings are no longer issued when setting up kexec. (BZ#1541285)
* When changing a kernel page mapping from Read Only (RO) to Read Write
(RW), the Translation Lookaside Buffer (TLB) entry was previously not
updated. Consequently, a protection fault on a write operation occurred,
which led to a kernel panic. With this update, the underlying source code
has been fixed to handle such kind of fault properly, and the kernel no
longer panics in the described situation. (BZ#1541892)
4. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- -------------------------------------------------------------------------
Debian Security Advisory DSA-4187-1 security@debian.org
https://www.debian.org/security/ Ben Hutchings
May 01, 2018 https://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : linux
CVE ID : CVE-2015-9016 CVE-2017-0861 CVE-2017-5715 CVE-2017-5753
CVE-2017-13166 CVE-2017-13220 CVE-2017-16526 CVE-2017-16911
CVE-2017-16912 CVE-2017-16913 CVE-2017-16914 CVE-2017-18017
CVE-2017-18203 CVE-2017-18216 CVE-2017-18232 CVE-2017-18241
CVE-2018-1066 CVE-2018-1068 CVE-2018-1092 CVE-2018-5332
CVE-2018-5333 CVE-2018-5750 CVE-2018-5803 CVE-2018-6927
CVE-2018-7492 CVE-2018-7566 CVE-2018-7740 CVE-2018-7757
CVE-2018-7995 CVE-2018-8781 CVE-2018-8822 CVE-2018-1000004
CVE-2018-1000199
Several vulnerabilities have been discovered in the Linux kernel that
may lead to a privilege escalation, denial of service or information
leaks.
CVE-2015-9016
Ming Lei reported a race condition in the multiqueue block layer
(blk-mq). On a system with a driver using blk-mq (mtip32xx,
null_blk, or virtio_blk), a local user might be able to use this
for denial of service or possibly for privilege escalation.
CVE-2017-0861
Robb Glasser reported a potential use-after-free in the ALSA (sound)
PCM core. We believe this was not possible in practice.
CVE-2017-5715
Multiple researchers have discovered a vulnerability in various
processors supporting speculative execution, enabling an attacker
controlling an unprivileged process to read memory from arbitrary
addresses, including from the kernel and all other processes
running on the system.
This specific attack has been named Spectre variant 2 (branch
target injection) and is mitigated for the x86 architecture (amd64
and i386) by using the "retpoline" compiler feature which allows
indirect branches to be isolated from speculative execution.
CVE-2017-5753
Multiple researchers have discovered a vulnerability in various
processors supporting speculative execution, enabling an attacker
controlling an unprivileged process to read memory from arbitrary
addresses, including from the kernel and all other processes
running on the system.
This specific attack has been named Spectre variant 1
(bounds-check bypass) and is mitigated by identifying vulnerable
code sections (array bounds checking followed by array access) and
replacing the array access with the speculation-safe
array_index_nospec() function.
More use sites will be added over time.
CVE-2017-13166
A bug in the 32-bit compatibility layer of the v4l2 ioctl handling
code has been found. Memory protections ensuring user-provided
buffers always point to userland memory were disabled, allowing
destination addresses to be in kernel space. On a 64-bit kernel a
local user with access to a suitable video device can exploit this
to overwrite kernel memory, leading to privilege escalation.
CVE-2017-13220
Al Viro reported that the Bluetooth HIDP implementation could
dereference a pointer before performing the necessary type check.
A local user could use this to cause a denial of service.
CVE-2017-16526
Andrey Konovalov reported that the UWB subsystem may dereference
an invalid pointer in an error case. A local user might be able
to use this for denial of service.
CVE-2017-16911
Secunia Research reported that the USB/IP vhci_hcd driver exposed
kernel heap addresses to local users. This information could aid the
exploitation of other vulnerabilities.
CVE-2017-16912
Secunia Research reported that the USB/IP stub driver failed to
perform a range check on a received packet header field, leading
to an out-of-bounds read. A remote user able to connect to the
USB/IP server could use this for denial of service.
CVE-2017-16913
Secunia Research reported that the USB/IP stub driver failed to
perform a range check on a received packet header field, leading
to excessive memory allocation. A remote user able to connect to
the USB/IP server could use this for denial of service.
CVE-2017-16914
Secunia Research reported that the USB/IP stub driver failed to
check for an invalid combination of fields in a received packet,
leading to a null pointer dereference. A remote user able to
connect to the USB/IP server could use this for denial of service.
CVE-2017-18017
Denys Fedoryshchenko reported that the netfilter xt_TCPMSS module
failed to validate TCP header lengths, potentially leading to a
use-after-free. If this module is loaded, it could be used by a
remote attacker for denial of service or possibly for code
execution.
CVE-2017-18203
Hou Tao reported that there was a race condition in creation and
deletion of device-mapper (DM) devices. A local user could
potentially use this for denial of service.
CVE-2017-18216
Alex Chen reported that the OCFS2 filesystem failed to hold a
necessary lock during nodemanager sysfs file operations,
potentially leading to a null pointer dereference. A local user
could use this for denial of service.
CVE-2017-18232
Jason Yan reported a race condition in the SAS (Serial-Attached
SCSI) subsystem, between probing and destroying a port. This
could lead to a deadlock. A physically present attacker could
use this to cause a denial of service.
CVE-2017-18241
Yunlei He reported that the f2fs implementation does not properly
initialise its state if the "noflush_merge" mount option is used.
A local user with access to a filesystem mounted with this option
could use this to cause a denial of service.
CVE-2018-1066
Dan Aloni reported to Red Hat that the CIFS client implementation
would dereference a null pointer if the server sent an invalid
response during NTLMSSP setup negotiation. This could be used
by a malicious server for denial of service.
CVE-2018-1068
The syzkaller tool found that the 32-bit compatibility layer of
ebtables did not sufficiently validate offset values. On a 64-bit
kernel, a local user with the CAP_NET_ADMIN capability (in any user
namespace) could use this to overwrite kernel memory, possibly
leading to privilege escalation. Debian disables unprivileged user
namespaces by default.
CVE-2018-1092
Wen Xu reported that a crafted ext4 filesystem image would
trigger a null dereference when mounted. A local user able
to mount arbitrary filesystems could use this for denial of
service.
CVE-2018-5332
Mohamed Ghannam reported that the RDS protocol did not
sufficiently validate RDMA requests, leading to an out-of-bounds
write. A local attacker on a system with the rds module loaded
could use this for denial of service or possibly for privilege
escalation.
CVE-2018-5333
Mohamed Ghannam reported that the RDS protocol did not properly
handle an error case, leading to a null pointer dereference. A
local attacker on a system with the rds module loaded could
possibly use this for denial of service.
CVE-2018-5750
Wang Qize reported that the ACPI sbshc driver logged a kernel heap
address. This information could aid the exploitation of other
vulnerabilities.
CVE-2018-5803
Alexey Kodanev reported that the SCTP protocol did not range-check
the length of chunks to be created. A local or remote user could
use this to cause a denial of service.
CVE-2018-6927
Li Jinyue reported that the FUTEX_REQUEUE operation on futexes did
not check for negative parameter values, which might lead to a
denial of service or other security impact.
CVE-2018-7492
The syzkaller tool found that the RDS protocol was lacking a null
pointer check. A local attacker on a system with the rds module
loaded could use this for denial of service.
CVE-2018-7566
Fan LongFei reported a race condition in the ALSA (sound)
sequencer core, between write and ioctl operations. This could
lead to an out-of-bounds access or use-after-free. A local user
with access to a sequencer device could use this for denial of
service or possibly for privilege escalation.
CVE-2018-7740
Nic Losby reported that the hugetlbfs filesystem's mmap operation
did not properly range-check the file offset. A local user with
access to files on a hugetlbfs filesystem could use this to cause
a denial of service.
CVE-2018-7757
Jason Yan reported a memory leak in the SAS (Serial-Attached
SCSI) subsystem. A local user on a system with SAS devices
could use this to cause a denial of service.
CVE-2018-7995
Seunghun Han reported a race condition in the x86 MCE
(Machine Check Exception) driver. This is unlikely to have
any security impact.
CVE-2018-8781
Eyal Itkin reported that the udl (DisplayLink) driver's mmap
operation did not properly range-check the file offset. A local
user with access to a udl framebuffer device could exploit this to
overwrite kernel memory, leading to privilege escalation.
CVE-2018-8822
Dr Silvio Cesare of InfoSect reported that the ncpfs client
implementation did not validate reply lengths from the server. An
ncpfs server could use this to cause a denial of service or
remote code execution in the client.
CVE-2018-1000004
Luo Quan reported a race condition in the ALSA (sound) sequencer
core, between multiple ioctl operations. This could lead to a
deadlock or use-after-free. A local user with access to a
sequencer device could use this for denial of service or possibly
for privilege escalation.
CVE-2018-1000199
Andy Lutomirski discovered that the ptrace subsystem did not
sufficiently validate hardware breakpoint settings. Local users
can use this to cause a denial of service, or possibly for
privilege escalation, on x86 (amd64 and i386) and possibly other
architectures.
For the oldstable distribution (jessie), these problems have been fixed
in version 3.16.56-1.
We recommend that you upgrade your linux packages.
For the detailed security status of linux please refer to its security
tracker page at:
https://security-tracker.debian.org/tracker/linux
Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/
Mailing list: debian-security-announce@lists.debian.org
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlron61fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND
z0Rtqw//Xf/L4bP65wU9M59Ef6xBt+Eph+yxeMsioGhu80ODdMemlmHzASMtfZjY
AXxyt9l8lbHn8MmwDA4aLhhwHYXwvKATdpHSy1SILrRfb4s9P9uV1vsHaIeZ649E
hDyNon9hP2tPso6BwqiYHZZy9Xxtd+T8vTBeBZwUKOLBkBRvV/gyNSUdJWp6L8WH
aF4D1hHl9ZotDkyIvkubbx77aqbJ88I4R0n69x7L9udFbuXa+U7hV6dJdnpzyl/7
OukJfEtnkaUgWu0MdOfFss6iH5OQISn/y/ricRi29oKQiEp3YwnT5J9pFwSQeJJS
H8ABVt251UoS0J+of3QWw0muOT/6UAF8SNpPKMJXC7Euq8pTmYVPSIeUYf4eqn65
UHZSCKXaszItq+uzVNYdkj504BJ4cG1lFxZtlrFWwKE8p7QOETN0GKvTRdu/SvDd
Hl2nb4HouLpBYS518Th2/MGgzhXXAuO12MH3smenptZbqxKn9Z0XSTJYzFupgJk/
kKF2xkDFBE4toTLVE+6XdUKwYk4vkeDZyOGOwRYThSkKAzrUh5zThgal4HnknD2A
5ye4XLhjgSIT47/nmor6lhxd7WGXGkV33GF0azYlHr/sclfzxcU2Ev3NUBWQ8M3s
CxfIO0FNCzO0WIUf40md7MlIAnDBIRGyYgNIIe7AnSRKKPykEx8=
=wNQS
-----END PGP SIGNATURE-----
. ==========================================================================
Ubuntu Security Notice USN-3597-1
March 15, 2018
linux, linux-raspi2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 17.10
Summary:
Several security issues were fixed in the Linux kernel. This flaw is known as Meltdown. This flaw is known as Spectre. (CVE-2017-5715,
CVE-2017-5753)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 17.10:
linux-image-4.13.0-1015-raspi2 4.13.0-1015.16
linux-image-4.13.0-37-generic 4.13.0-37.42
linux-image-4.13.0-37-generic-lpae 4.13.0-37.42
linux-image-4.13.0-37-lowlatency 4.13.0-37.42
linux-image-generic 4.13.0.37.40
linux-image-generic-lpae 4.13.0.37.40
linux-image-lowlatency 4.13.0.37.40
linux-image-raspi2 4.13.0.1015.13
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Note: the current version of the following document is available here:
https://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-hpesbhf03805en_us
SUPPORT COMMUNICATION - SECURITY BULLETIN
Document ID: hpesbhf03805en_us
Version: 4
HPESBHF03805 rev.4 - Certain HPE products using Microprocessors from Intel,
AMD, and ARM, with Speculative Execution, Elevation of Privilege and
Information Disclosure.
NOTICE: The information in this Security Bulletin should be acted upon as
soon as possible.
Release Date: 2018-01-10
Last Updated: 2018-01-09
Potential Security Impact: Local: Disclosure of Information, Elevation of
Privilege
Source: Hewlett Packard Enterprise, Product Security Response Team
VULNERABILITY SUMMARY
On January 3 2018, side-channel security vulnerabilities involving
speculative execution were publicly disclosed. These vulnerabilities may
impact the listed HPE products, potentially leading to information disclosure
and elevation of privilege. Mitigation and resolution of these
vulnerabilities may call for both an operating system update, provided by the
OS vendor, and a system ROM update from HPE.
**Note:**
* This issue takes advantage of techniques commonly used in many modern
processor architectures.
* For further information, microprocessor vendors have provided security
advisories:
- Intel:
<https://security-center.intel.com/advisory.aspx?intelid=intel-sa-00088&langu
geid=en-fr>
- AMD: <http://www.amd.com/en/corporate/speculative-execution>
- ARM: <https://developer.arm.com/support/security-update>
References:
- PSRT110634
- PSRT110633
- PSRT110632
- CVE-2017-5715 - aka Spectre, branch target injection
- CVE-2017-5753 - aka Spectre, bounds check bypass
- CVE-2017-5754 - aka Meltdown, rogue data cache load, memory access
permission check performed after kernel memory read
SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed.
- HPE ProLiant DL380 Gen10 Server prior to v1.28
- HPE ProLiant DL180 Gen10 Server prior to v1.28
- HPE ProLiant DL160 Gen10 Server prior to v1.28
- HPE ProLiant DL360 Gen10 Server prior to v1.28
- HPE ProLiant ML110 Gen10 Server prior to v1.28
- HPE ProLiant DL580 Gen10 Server prior to v1.28
- HPE ProLiant DL560 Gen10 Server prior to v1.28
- HPE ProLiant DL120 Gen10 Server prior to v1.28
- HPE ProLiant ML350 Gen10 Server prior to v1.28
- HPE ProLiant XL450 Gen10 Server prior to v1.28
- HPE ProLiant XL170r Gen10 Server prior to v1.28
- HPE ProLiant BL460c Gen10 Server Blade prior to v1.28
- HPE ProLiant XL230a Gen9 Server prior to v2.54
- HPE ProLiant XL230k Gen10 Server prior to v1.28
- HPE ProLiant XL730f Gen9 Server prior to v2.54
- HPE ProLiant XL740f Gen9 Server prior to v2.54
- HPE ProLiant XL750f Gen9 Server prior to v2.54
- HPE ProLiant XL170r Gen9 Server prior to v2.54
- HP ProLiant DL60 Gen9 Server prior to v2.54
- HPE ProLiant XL450 Gen9 Server prior to v2.54
- HP ProLiant DL160 Gen9 Server prior to v2.54
- HPE Apollo 4200 Gen9 Server prior to v2.54
- HP ProLiant BL460c Gen9 Server Blade prior to v2.54
- HP ProLiant ML110 Gen9 Server prior to v2.54
- HP ProLiant ML150 Gen9 Server prior to v2.54
- HPE ProLiant ML350 Gen9 Server prior to v2.54
- HP ProLiant DL380 Gen9 Server prior to v2.54
- HP ProLiant DL120 Gen9 Server prior to v2.54
- HPE ProLiant DL560 Gen9 Server prior to v2.54
- HPE ProLiant XL270d Gen9 Special Server prior to v2.54
- HP ProLiant BL660c Gen9 Server prior to v2.54
- HPE ProLiant m710x Server Cartridge prior to v1.60
- HPE ProLiant DL20 Gen9 Server prior to v2.52
- HPE ProLiant DL385 Gen10 Server prior to v1.04
- HPE Synergy 660 Gen9 Compute Module prior to v2.54
- HPE Synergy 480 Gen10 Compute Module prior to v1.28
- HPE Synergy 480 Gen9 Compute Module prior to v2.54
- HPE ProLiant ML30 Gen9 Server prior to v2.52
- HPE ProLiant XL190r Gen10 Server prior to v1.28
- HPE ProLiant XL250a Gen9 Server prior to v2.54
- HPE ProLiant XL190r Gen9 Server prior to v2.54
- HP ProLiant DL80 Gen9 Server prior to v2.54
- HPE ProLiant DL180 Gen9 Server prior to v2.54
- HPE ProLiant XL270d Gen9 Accelerator Tray 2U Configure-to-order Server
prior to v2.54
- HPE ProLiant WS460c Gen9 Workstation prior to v2.54
- HPE ProLiant DL580 Gen9 Special Server prior to v2.54
- HPE Synergy 680 Gen9 Compute Modules prior to v2.54
- HPE ProLiant XL260a Gen9 Server prior to 1/22/2018
- HPE ProLiant m510 Server Cartridge prior to 1/22/2018
- HPE ProLiant m710p Server Cartridge prior to 12/12/2017
- HP ProLiant m350 Server Cartridge prior to 12/12/2017
- HP ProLiant m300 Server Cartridge prior to 12/12/2017
- HP ProLiant ML350e Gen8 Server prior to 12/12/2017
- HPE ProLiant ML350e Gen8 v2 Server prior to 12/12/2017
- HP ProLiant BL460c Gen8 Server prior to 12/12/2017
- HP ProLiant BL660c Gen8 Server prior to 12/12/2017
- HPE ProLiant SL4540 Gen8 1 Node Server prior to 12/12/2017
- HP ProLiant DL380e Gen8 Server prior to 12/12/2017
- HP ProLiant DL360e Gen8 Server prior to 12/12/2017
- HP ProLiant ML350p Gen8 Server prior to 12/12/2017
- HP ProLiant DL360p Gen8 Server prior to 12/12/2017
- HP ProLiant DL380p Gen8 Server prior to 12/12/2017
- HP ProLiant DL320e Gen8 Server prior to 12/12/2017
- HPE ProLiant DL320e Gen8 v2 Server prior to 12/12/2017
- HP ProLiant ML310e Gen8 Server prior to 12/12/2017
- HPE ProLiant ML310e Gen8 v2 Server prior to 12/12/2017
- HP ProLiant DL160 Gen8 Server prior to 12/12/2017
- HP ProLiant SL270s Gen8 Server prior to 12/12/2017
- HP ProLiant SL250s Gen8 Server prior to 12/12/2017
- HP ProLiant SL230s Gen8 Server prior to 12/12/2017
- HP ProLiant DL560 Gen8 Server prior to 12/12/2017
- HPE ProLiant SL210t Gen8 Server prior to 12/12/2017
- HP ProLiant DL580 Gen8 Server prior to 12/12/2017 (v1.98)
- HP ProLiant ML10 Server prior to 12/12/2017
- HP ProLiant m710 Server Cartridge prior to 12/12/2017 (v1.60)
- HPE Synergy Composer prior to 12/12/2017
- HPE Integrity Superdome X with BL920s Blades prior to 8.8.6
- HPE Superdome Flex Server prior to 2.3.110
- HP ProLiant DL360 Gen9 Server prior to v2.54
- HPE Synergy 620 Gen9 Compute Module prior to v2.54
- HPE ProLiant Thin Micro TM200 Server prior to 1/16/2017
- HPE ProLiant ML350 Gen10 Server prior to v1.28
- HP ProLiant BL420c Gen8 Server prior to 12/12/2017
- HPE ProLiant ML10 v2 Server prior to 12/12/2017
- HPE ProLiant MicroServer Gen8 prior to 12/12/2017
- HPE Synergy 660 Gen10 Compute Module prior to v1.28
BACKGROUND
CVSS Base Metrics
=================
Reference, CVSS V3 Score/Vector, CVSS V2 Score/Vector
CVE-2017-5715
8.2 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
6.8 (AV:A/AC:L/Au:N/C:C/I:P/A:N)
CVE-2017-5753
5.0 CVSS:3.0/AV:A/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
5.4 (AV:A/AC:M/Au:N/C:P/I:P/A:P)
CVE-2017-5754
7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
7.8 (AV:N/AC:L/Au:N/C:C/I:N/A:N)
Information on CVSS is documented in
HPE Customer Notice HPSN-2008-002 here:
https://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01345499
RESOLUTION
HPE has made the following system ROM updates which include an updated
microcode to resolve the vulnerability:
* HPE has provided a customer bulletin
<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00039267en_us>
with specific instructions to obtain the udpated sytem ROM
- Note:
+ CVE-2017-5715 requires that the System ROM be updated and a vendor
supplied operating system update be applied as well.
+ For CVE-2017-5753, CVE-2017-5754 require only updates of a vendor
supplied operating system.
+ HPE will continue to add additional products to the list. Not all
listed products have updated system ROMs yet. Impacted products awaiting
system ROM updates are marked TBS (to be supplied).
HISTORY
Version:1 (rev.1) - 4 January 2018 Initial release
Version:2 (rev.2) - 5 January 2018 Added additional impacted products
Version:3 (rev.3) - 10 January 2018 Added more impacted products
Version:4 (rev.4) - 9 January 2018 Fixed product ID
Third Party Security Patches: Third party security patches that are to be
installed on systems running Hewlett Packard Enterprise (HPE) software
products should be applied in accordance with the customer's patch management
policy.
Support: For issues about implementing the recommendations of this Security
Bulletin, contact normal HPE Services support channel. For other issues about
the content of this Security Bulletin, send e-mail to security-alert@hpe.com.
Report: To report a potential security vulnerability for any HPE supported
product:
Web form: https://www.hpe.com/info/report-security-vulnerability
Email: security-alert@hpe.com
Subscribe: To initiate a subscription to receive future HPE Security Bulletin
alerts via Email: http://www.hpe.com/support/Subscriber_Choice
Security Bulletin Archive: A list of recently released Security Bulletins is
available here: http://www.hpe.com/support/Security_Bulletin_Archive
Software Product Category: The Software Product Category is represented in
the title by the two characters following HPSB.
3C = 3COM
3P = 3rd Party Software
GN = HPE General Software
HF = HPE Hardware and Firmware
MU = Multi-Platform Software
NS = NonStop Servers
OV = OpenVMS
PV = ProCurve
ST = Storage Software
UX = HP-UX
Copyright 2016 Hewlett Packard Enterprise
Hewlett Packard Enterprise shall not be liable for technical or editorial
errors or omissions contained herein. The information provided is provided
"as is" without warranty of any kind. To the extent permitted by law, neither
HP or its affiliates, subcontractors or suppliers will be liable for
incidental,special or consequential damages including downtime cost; lost
profits; damages relating to the procurement of substitute products or
services; or damages for loss of data, or software restoration. The
information in this document is subject to change without notice. Hewlett
Packard Enterprise and the names of Hewlett Packard Enterprise products
referenced herein are trademarks of Hewlett Packard Enterprise in the United
States and other countries. Other product and company names mentioned herein
may be trademarks of their respective owners. Summary
VMware Virtual Appliance updates address side-channel analysis due
to speculative execution
Note:
This document will focus on VMware Virtual Appliances which are
affected by the known variants of CVE-2017-5753, CVE-2017-5715, and
CVE-2017-5754. For more information please see Knowledge Base article
52264.
These mitigations are part of the Operating System-Specific
Mitigations category described in VMware Knowledge Base article
52245. Relevant Products
vCloud Usage Meter (UM)
Identity Manager (vIDM)
vCenter Server (vCSA)
vSphere Data Protection (VDP)
vSphere Integrated Containers (VIC)
vRealize Automation (vRA)
3.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the identifiers CVE-2017-5753 (Bounds Check bypass),
CVE-2017-5715 (Branch Target Injection), CVE-2017-5754 (Rogue data
cache load) to these issues.
Column 5 of the following table lists the action required to
mitigate the observed vulnerability in each release, if a solution
is available.
VMware Product Running Replace with/ Mitigation/
Product Version on Severity Apply Patch Workaround
========== ========= ======= ========= ============= ==========
UM 3.x VA Important Patch Pending KB52467
vIDM 3.x, 2.x VA Important Patch Pending KB52284
vCSA 6.5 VA Important Patch Pending KB52312
vCSA 6.0 VA Important Patch Pending KB52312
vCSA 5.5 VA N/A Unaffected None
VDP 6.x VA Important Patch Pending None
VIC 1.x VA Important 1.3.1 None
vRA 7.x VA Important Patch Pending KB52377
vRA 6.x VA Important Patch Pending KB52497
4. Solution
Please review the patch/release notes for your product and version
and verify the checksum of your downloaded file.
vSphere Integrated Containers 1.3.1
Downloads and Documentation:
https://my.vmware.com/group/vmware/get-download?downloadGroup=VIC131
5. Change log
2018-02-08: VMSA-2018-0007
Initial security advisory in conjunction with the release of vSphere
Integrated Containers 1.3.1 on 2018-02-08. Contact
E-mail list for product security notifications and announcements:
http://lists.vmware.com/cgi-bin/mailman/listinfo/security-announce
This Security Advisory is posted to the following lists:
security-announce@lists.vmware.com
bugtraq@securityfocus.com
fulldisclosure@seclists.org
E-mail: security at vmware.com
PGP key at: https://kb.vmware.com/kb/1055
VMware Security Advisories
http://www.vmware.com/security/advisories
VMware Security Response Policy
https://www.vmware.com/support/policies/security_response.html
VMware Lifecycle Support Phases
https://www.vmware.com/support/policies/lifecycle.html
VMware Security & Compliance Blog
https://blogs.vmware.com/security
Twitter
https://twitter.com/VMwareSRC
Copyright 2018 VMware Inc. All rights reserved. Ubuntu is working with Intel and AMD to provide
future microcode updates that implement IBRS and IBPB as they are made
available. Ubuntu users with a processor from a different vendor should
contact the vendor to identify necessary firmware updates. Ubuntu
will provide corresponding QEMU updates in the future for users of
self-hosted virtual environments in coordination with upstream QEMU.
Ubuntu users in cloud environments should contact the cloud provider
to confirm that the hypervisor has been updated to expose the new
CPU features to virtual machines.
Background
==========
Xen is a bare-metal hypervisor.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-emulation/xen < 4.10.1-r2 >= 4.10.1-r2
2 app-emulation/xen-tools < 4.10.1-r2 >= 4.10.1-r2
-------------------------------------------------------------------
2 affected packages
Description
===========
Multiple vulnerabilities have been discovered in Xen. Please review the
referenced CVE identifiers for details.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Xen users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-emulation/xen-4.10.1-r2"
All Xen tools users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=app-emulation/xen-tools-4.10.1-r2"
References
==========
[ 1 ] CVE-2017-5715
https://nvd.nist.gov/vuln/detail/CVE-2017-5715
[ 2 ] CVE-2017-5753
https://nvd.nist.gov/vuln/detail/CVE-2017-5753
[ 3 ] CVE-2017-5754
https://nvd.nist.gov/vuln/detail/CVE-2017-5754
[ 4 ] CVE-2018-10471
https://nvd.nist.gov/vuln/detail/CVE-2018-10471
[ 5 ] CVE-2018-10472
https://nvd.nist.gov/vuln/detail/CVE-2018-10472
[ 6 ] CVE-2018-10981
https://nvd.nist.gov/vuln/detail/CVE-2018-10981
[ 7 ] CVE-2018-10982
https://nvd.nist.gov/vuln/detail/CVE-2018-10982
[ 8 ] CVE-2018-12891
https://nvd.nist.gov/vuln/detail/CVE-2018-12891
[ 9 ] CVE-2018-12892
https://nvd.nist.gov/vuln/detail/CVE-2018-12892
[ 10 ] CVE-2018-12893
https://nvd.nist.gov/vuln/detail/CVE-2018-12893
[ 11 ] CVE-2018-15468
https://nvd.nist.gov/vuln/detail/CVE-2018-15468
[ 12 ] CVE-2018-15469
https://nvd.nist.gov/vuln/detail/CVE-2018-15469
[ 13 ] CVE-2018-15470
https://nvd.nist.gov/vuln/detail/CVE-2018-15470
[ 14 ] CVE-2018-3620
https://nvd.nist.gov/vuln/detail/CVE-2018-3620
[ 15 ] CVE-2018-3646
https://nvd.nist.gov/vuln/detail/CVE-2018-3646
[ 16 ] CVE-2018-5244
https://nvd.nist.gov/vuln/detail/CVE-2018-5244
[ 17 ] CVE-2018-7540
https://nvd.nist.gov/vuln/detail/CVE-2018-7540
[ 18 ] CVE-2018-7541
https://nvd.nist.gov/vuln/detail/CVE-2018-7541
[ 19 ] CVE-2018-7542
https://nvd.nist.gov/vuln/detail/CVE-2018-7542
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201810-06
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2018 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
. 7.2) - noarch, x86_64
3. Summary:
An update for kernel is now available for Red Hat Enterprise Linux 6.
Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.
2. Relevant releases/architectures:
Red Hat Enterprise Linux Desktop (v. 6) - i386, noarch, x86_64
Red Hat Enterprise Linux Desktop Optional (v. 6) - i386, x86_64
Red Hat Enterprise Linux HPC Node (v. 6) - noarch, x86_64
Red Hat Enterprise Linux HPC Node Optional (v. 6) - x86_64
Red Hat Enterprise Linux Server (v. 6) - i386, noarch, ppc64, s390x, x86_64
Red Hat Enterprise Linux Server Optional (v. 6) - i386, ppc64, s390x, x86_64
Red Hat Enterprise Linux Workstation (v. 6) - i386, noarch, x86_64
Red Hat Enterprise Linux Workstation Optional (v. 6) - i386, x86_64
3.
Security Fix(es):
An industry-wide issue was found in the way many modern microprocessor
designs have implemented speculative execution of instructions (a commonly
used performance optimization). There are three primary variants of the
issue which differ in the way the speculative execution can be exploited.
Note: This issue is present in hardware and cannot be fully fixed via
software update. The updated kernel packages provide software mitigation
for this hardware issue at a cost of potential performance penalty. Please
refer to References section for further information about this issue and
the performance impact.
In this update mitigations for x86-64 architecture are provided.
Variant CVE-2017-5753 triggers the speculative execution by performing a
bounds-check bypass. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
boundary and read privileged memory by conducting targeted cache
side-channel attacks. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
and guest/host boundaries and read privileged memory by conducting targeted
cache side-channel attacks. (CVE-2017-5715, Important)
Variant CVE-2017-5754 relies on the fact that, on impacted microprocessors,
during speculative execution of instruction permission faults, exception
generation triggered by a faulting access is suppressed until the
retirement of the whole instruction block. In a combination with the fact
that memory accesses may populate the cache even when the block is being
dropped and never committed (executed), an unprivileged local attacker
could use this flaw to read privileged (kernel space) memory by conducting
targeted cache side-channel attacks. (CVE-2017-5754, Important)
Note: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64
microprocessors are not affected by this issue.
Red Hat would like to thank Google Project Zero for reporting these issues.
4. Solution:
For details on how to apply this update, which includes the changes
described in this advisory, refer to:
https://access.redhat.com/articles/11258
The system must be rebooted for this update to take effect.
5. Bugs fixed (https://bugzilla.redhat.com/):
1519778 - CVE-2017-5753 hw: cpu: speculative execution bounds-check bypass
1519780 - CVE-2017-5715 hw: cpu: speculative execution branch target injection
1519781 - CVE-2017-5754 hw: cpu: speculative execution permission faults handling
6. Package List:
Red Hat Enterprise Linux Desktop (v. 6):
Source:
kernel-2.6.32-696.18.7.el6.src.rpm
i386:
kernel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-headers-2.6.32-696.18.7.el6.i686.rpm
perf-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
kernel-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-headers-2.6.32-696.18.7.el6.x86_64.rpm
perf-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux Desktop Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux HPC Node (v. 6):
Source:
kernel-2.6.32-696.18.7.el6.src.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
kernel-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-headers-2.6.32-696.18.7.el6.x86_64.rpm
perf-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux HPC Node Optional (v. 6):
x86_64:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux Server (v. 6):
Source:
kernel-2.6.32-696.18.7.el6.src.rpm
i386:
kernel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-headers-2.6.32-696.18.7.el6.i686.rpm
perf-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
ppc64:
kernel-2.6.32-696.18.7.el6.ppc64.rpm
kernel-bootwrapper-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debug-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debuginfo-common-ppc64-2.6.32-696.18.7.el6.ppc64.rpm
kernel-devel-2.6.32-696.18.7.el6.ppc64.rpm
kernel-headers-2.6.32-696.18.7.el6.ppc64.rpm
perf-2.6.32-696.18.7.el6.ppc64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
s390x:
kernel-2.6.32-696.18.7.el6.s390x.rpm
kernel-debug-2.6.32-696.18.7.el6.s390x.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.s390x.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
kernel-debuginfo-common-s390x-2.6.32-696.18.7.el6.s390x.rpm
kernel-devel-2.6.32-696.18.7.el6.s390x.rpm
kernel-headers-2.6.32-696.18.7.el6.s390x.rpm
kernel-kdump-2.6.32-696.18.7.el6.s390x.rpm
kernel-kdump-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
kernel-kdump-devel-2.6.32-696.18.7.el6.s390x.rpm
perf-2.6.32-696.18.7.el6.s390x.rpm
perf-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
x86_64:
kernel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
kernel-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-headers-2.6.32-696.18.7.el6.x86_64.rpm
perf-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux Server Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
ppc64:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
kernel-debuginfo-common-ppc64-2.6.32-696.18.7.el6.ppc64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
python-perf-2.6.32-696.18.7.el6.ppc64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.ppc64.rpm
s390x:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
kernel-debuginfo-common-s390x-2.6.32-696.18.7.el6.s390x.rpm
kernel-kdump-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
perf-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
python-perf-2.6.32-696.18.7.el6.s390x.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.s390x.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux Workstation (v. 6):
Source:
kernel-2.6.32-696.18.7.el6.src.rpm
i386:
kernel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-headers-2.6.32-696.18.7.el6.i686.rpm
perf-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
kernel-debug-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
kernel-devel-2.6.32-696.18.7.el6.x86_64.rpm
kernel-headers-2.6.32-696.18.7.el6.x86_64.rpm
perf-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
Red Hat Enterprise Linux Workstation Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.18.7.el6.i686.rpm
perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
python-perf-2.6.32-696.18.7.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.i686.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.18.7.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-2.6.32-696.18.7.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.18.7.el6.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/
7. References:
https://access.redhat.com/security/updates/classification/#important
https://access.redhat.com/security/vulnerabilities/speculativeexecution
https://access.redhat.com/security/cve/CVE-2017-5753
https://access.redhat.com/security/cve/CVE-2017-5715
https://access.redhat.com/security/cve/CVE-2017-5754
8. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2018 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFaTXwuXlSAg2UNWIIRAp3LAKCNdSqjVu7zsXcUTnpGuuQAuUlTpwCfTE/O
OR+iGnoY+cALbsBWKwbmzQM=
=V4ow
-----END PGP SIGNATURE-----
--
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce
| VAR-201801-1711 | CVE-2017-5754 | CPU hardware utilizing speculative execution may be vulnerable to cache side-channel attacks |
CVSS V2: 4.7 CVSS V3: 5.6 Severity: MEDIUM |
Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache. Two vulnerabilities are identified, known as "Variant 3a" and "Variant 4". CPUhardware is a set of firmware that runs in the CPU (Central Processing Unit) for managing and controlling the CPU. The Spectre vulnerability exists in the CPU processor core. Because Intel does not separate low-privileged applications from accessing kernel memory, an attacker can use a malicious application to obtain private data that should be quarantined. Intel and ARM CPU chips have an information disclosure vulnerability, which originates from a flaw in the processor data boundary mechanism. The following products and versions are affected: ARM Cortex-A75; Intel Xeon E5-1650 v3, v2, v4; Xeon E3-1265l v2, v3, v4; Xeon E3-1245 v2, v3, v5, v6; Xeon X7542 wait. 6.6) - noarch, x86_64
3.
Security Fix(es):
* hw: cpu: speculative execution permission faults handling (CVE-2017-5754)
* Kernel: error in exception handling leads to DoS (CVE-2018-8897)
For more details about the security issue(s), including the impact, a CVSS
score, and other related information, refer to the CVE page(s) listed in
the References section.
Bug Fix(es):
* If an NFSv3 client mounted a subdirectory of an exported file system, a
directory entry to the mount hosting the export was incorrectly held even
after clearing the cache. Consequently, attempts to unmount the
subdirectory with the umount command failed with the EBUSY error. With this
update, the underlying source code has been fixed, and the unmount
operation now succeeds as expected in the described situation. (BZ#1538588)
* The kernel build requirements have been updated to the GNU Compiler
Collection (GCC) compiler version that has the support for Retpolines. The
Retpolines mechanism is a software construct that leverages specific
knowledge of the underlying hardware to mitigate the branch target
injection, also known as Spectre variant 2 vulnerability described in
CVE-2017-5715. (BZ#1554254)
4. On i386 and amd64
architectures, the IBRS and IBPB features are required to enable the
kernel mitigations. Ubuntu is working with Intel and AMD to provide
future microcode updates that implement IBRS and IBPB as they are made
available. Ubuntu users with a processor from a different vendor should
contact the vendor to identify necessary firmware updates. Ubuntu
will provide corresponding QEMU updates in the future for users of
self-hosted virtual environments in coordination with upstream QEMU.
Ubuntu users in cloud environments should contact the cloud provider
to confirm that the hypervisor has been updated to expose the new
CPU features to virtual machines. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Note: the current version of the following document is available here:
https://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-hpesbhf03805en_us
SUPPORT COMMUNICATION - SECURITY BULLETIN
Document ID: hpesbhf03805en_us
Version: 5
HPESBHF03805 rev.5 - Certain HPE products using Microprocessors from Intel,
AMD, and ARM, with Speculative Execution, Elevation of Privilege and
Information Disclosure.
NOTICE: The information in this Security Bulletin should be acted upon as
soon as possible.
Release Date: 2018-01-18
Last Updated: 2018-01-17
Potential Security Impact: Local: Disclosure of Information, Elevation of
Privilege
Source: Hewlett Packard Enterprise, Product Security Response Team
VULNERABILITY SUMMARY
On January 3 2018, side-channel security vulnerabilities involving
speculative execution were publicly disclosed. These vulnerabilities may
impact the listed HPE products, potentially leading to information disclosure
and elevation of privilege. Mitigation and resolution of these
vulnerabilities may call for both an operating system update, provided by the
OS vendor, and a system ROM update from HPE.
**Note:**
* This issue takes advantage of techniques commonly used in many modern
processor architectures.
* For further information, microprocessor vendors have provided security
advisories:
- Intel:
<https://security-center.intel.com/advisory.aspx?intelid=intel-sa-00088&langu
geid=en-fr>
- AMD: <http://www.amd.com/en/corporate/speculative-execution>
- ARM: <https://developer.arm.com/support/security-update>
References:
- PSRT110635
- PSRT110634
- PSRT110633
- PSRT110632
- CVE-2017-5715 - aka Spectre, branch target injection
- CVE-2017-5753 - aka Spectre, bounds check bypass
- CVE-2017-5754 - aka Meltdown, rogue data cache load, memory access
permission check performed after kernel memory read
SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed.
- HPE ProLiant DL380 Gen10 Server prior to v1.28
- HPE ProLiant DL180 Gen10 Server prior to v1.28
- HPE ProLiant DL160 Gen10 Server prior to v1.28
- HPE ProLiant DL360 Gen10 Server prior to v1.28
- HPE ProLiant ML110 Gen10 Server prior to v1.28
- HPE ProLiant DL580 Gen10 Server prior to v1.28
- HPE ProLiant DL560 Gen10 Server prior to v1.28
- HPE ProLiant DL120 Gen10 Server prior to v1.28
- HPE ProLiant ML350 Gen10 Server prior to v1.28
- HPE ProLiant XL450 Gen10 Server prior to v1.28
- HPE Synergy 660 Gen10 Compute Module prior to v1.28
- HPE ProLiant XL170r Gen10 Server prior to v1.28
- HPE ProLiant BL460c Gen10 Server Blade prior to v1.28
- HPE ProLiant XL190r Gen10 Server prior to v1.28
- HPE ProLiant XL230k Gen10 Server prior to v1.28
- HPE ProLiant DL385 Gen10 Server prior to v1.04
- HPE Synergy 480 Gen10 Compute Module prior to v1.28
- HPE ProLiant ML350 Gen10 Server prior to v1.28
- HPE ProLiant XL730f Gen9 Server To be delivered
- HPE ProLiant XL230a Gen9 Server To be delivered
- HPE ProLiant XL740f Gen9 Server To be delivered
- HPE ProLiant XL750f Gen9 Server To be delivered
- HPE ProLiant XL170r Gen9 Server To be delivered
- HP ProLiant DL60 Gen9 Server To be delivered
- HPE ProLiant XL450 Gen9 Server To be delivered
- HP ProLiant DL160 Gen9 Server To be delivered
- HPE Apollo 4200 Gen9 Server To be delivered
- HP ProLiant BL460c Gen9 Server Blade To be delivered
- HP ProLiant ML110 Gen9 Server To be delivered
- HP ProLiant ML150 Gen9 Server To be delivered
- HPE ProLiant ML350 Gen9 Server To be delivered
- HP ProLiant DL380 Gen9 Server To be delivered
- HP ProLiant DL120 Gen9 Server To be delivered
- HPE ProLiant DL560 Gen9 Server To be delivered
- HP ProLiant BL660c Gen9 Server To be delivered
- HPE ProLiant DL20 Gen9 Server To be delivered
- HPE Synergy 660 Gen9 Compute Module To be delivered
- HPE Synergy 480 Gen9 Compute Module To be delivered
- HPE ProLiant ML30 Gen9 Server To be delivered
- HPE ProLiant XL250a Gen9 Server To be delivered
- HPE ProLiant XL190r Gen9 Server To be delivered
- HP ProLiant DL80 Gen9 Server To be delivered
- HPE ProLiant DL180 Gen9 Server To be delivered
- HPE ProLiant XL270d Gen9 Accelerator Tray 2U Configure-to-order Server To
be delivered
- HPE ProLiant WS460c Gen9 Workstation To be delivered
- HPE ProLiant XL260a Gen9 Server To be delivered
- HPE Synergy 620 Gen9 Compute Module To be delivered
- HPE ProLiant DL580 Gen9 Server To be delivered
- HPE Synergy 680 Gen9 Compute Module To be delivered
- HPE ProLiant m510 Server Cartridge prior to v1.62
- HPE ProLiant m710p Server Cartridge prior to v12/12/2017
- HPE ProLiant m710x Server Cartridge prior to v1.60
- HP ProLiant m710 Server Cartridge prior to 12/12/2017 (v1.60)
- HPE Synergy Composer prior to 12/12/2017
- HPE Integrity Superdome X with BL920s Blades prior to 8.8.6
- HP ProLiant DL360 Gen9 Server prior to 2.3.110
- HPE ProLiant Thin Micro TM200 Server prior to 1/16/2017
- HPE ProLiant ML10 v2 Server prior to 12/12/2017
- HPE ProLiant m350 Server Cartridge prior to v1/15/2018
- HPE ProLiant m300 Server Cartridge prior to v1/15/2018
- HPE ProLiant MicroServer Gen8 prior to 12/12/2017
- HPE ProLiant ML310e Gen8 v2 Server prior to v12/12/2017
BACKGROUND
CVSS Base Metrics
=================
Reference, CVSS V3 Score/Vector, CVSS V2 Score/Vector
CVE-2017-5715
8.2 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
6.8 (AV:A/AC:L/Au:N/C:C/I:P/A:N)
CVE-2017-5753
5.0 CVSS:3.0/AV:A/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
5.4 (AV:A/AC:M/Au:N/C:P/I:P/A:P)
CVE-2017-5754
7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
7.8 (AV:N/AC:L/Au:N/C:C/I:N/A:N)
Information on CVSS is documented in
HPE Customer Notice HPSN-2008-002 here:
https://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01345499
RESOLUTION
HPE has made the following system ROM updates which include an updated
microcode to resolve the vulnerability:
* HPE has provided a customer bulletin
<https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00039267en_us>
with specific instructions to obtain the udpated sytem ROM
- Note:
+ CVE-2017-5715 (Variant 2) requires that the System ROM be updated and a
vendor supplied operating system update be applied as well.
+ For CVE-2017-5753, CVE-2017-5754 (Variants 1 and 3) require only
updates of a vendor supplied operating system.
+ HPE will continue to add additional products to the list.
HISTORY
Version:1 (rev.1) - 4 January 2018 Initial release
Version:2 (rev.2) - 5 January 2018 Added additional impacted products
Version:3 (rev.3) - 10 January 2018 Added more impacted products
Version:4 (rev.4) - 9 January 2018 Fixed product ID
Version:5 (rev.5) - 18 January 2018 Added additional impacted products
Third Party Security Patches: Third party security patches that are to be
installed on systems running Hewlett Packard Enterprise (HPE) software
products should be applied in accordance with the customer's patch management
policy.
Support: For issues about implementing the recommendations of this Security
Bulletin, contact normal HPE Services support channel. For other issues about
the content of this Security Bulletin, send e-mail to security-alert@hpe.com.
Report: To report a potential security vulnerability for any HPE supported
product:
Web form: https://www.hpe.com/info/report-security-vulnerability
Email: security-alert@hpe.com
Subscribe: To initiate a subscription to receive future HPE Security Bulletin
alerts via Email: http://www.hpe.com/support/Subscriber_Choice
Security Bulletin Archive: A list of recently released Security Bulletins is
available here: http://www.hpe.com/support/Security_Bulletin_Archive
Software Product Category: The Software Product Category is represented in
the title by the two characters following HPSB.
3C = 3COM
3P = 3rd Party Software
GN = HPE General Software
HF = HPE Hardware and Firmware
MU = Multi-Platform Software
NS = NonStop Servers
OV = OpenVMS
PV = ProCurve
ST = Storage Software
UX = HP-UX
Copyright 2016 Hewlett Packard Enterprise
Hewlett Packard Enterprise shall not be liable for technical or editorial
errors or omissions contained herein. The information provided is provided
"as is" without warranty of any kind. To the extent permitted by law, neither
HP or its affiliates, subcontractors or suppliers will be liable for
incidental,special or consequential damages including downtime cost; lost
profits; damages relating to the procurement of substitute products or
services; or damages for loss of data, or software restoration. The
information in this document is subject to change without notice. Hewlett
Packard Enterprise and the names of Hewlett Packard Enterprise products
referenced herein are trademarks of Hewlett Packard Enterprise in the United
States and other countries. Other product and company names mentioned herein
may be trademarks of their respective owners. Unfortunately, that update introduced
a regression where a few systems failed to boot successfully. This
update fixes the problem.
We apologize for the inconvenience.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=====================================================================
Red Hat Security Advisory
Synopsis: Important: kernel security and bug fix update
Advisory ID: RHSA-2018:0151-01
Product: Red Hat Enterprise Linux
Advisory URL: https://access.redhat.com/errata/RHSA-2018:0151
Issue date: 2018-01-25
CVE Names: CVE-2015-8539 CVE-2017-7472 CVE-2017-12192
CVE-2017-12193 CVE-2017-15649
=====================================================================
1. Summary:
An update for kernel is now available for Red Hat Enterprise Linux 7.
Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.
2. Relevant releases/architectures:
Red Hat Enterprise Linux Client (v. 7) - noarch, x86_64
Red Hat Enterprise Linux Client Optional (v. 7) - x86_64
Red Hat Enterprise Linux ComputeNode (v. 7) - noarch, x86_64
Red Hat Enterprise Linux ComputeNode Optional (v. 7) - x86_64
Red Hat Enterprise Linux Server (v. 7) - noarch, ppc64, ppc64le, s390x, x86_64
Red Hat Enterprise Linux Server Optional (v. 7) - ppc64, ppc64le, x86_64
Red Hat Enterprise Linux Workstation (v. 7) - noarch, x86_64
Red Hat Enterprise Linux Workstation Optional (v. 7) - x86_64
3.
Security Fix(es):
An industry-wide issue was found in the way many modern microprocessor
designs have implemented speculative execution of instructions (a commonly
used performance optimization). There are three primary variants of the
issue which differ in the way the speculative execution can be exploited.
Note: This issue is present in hardware and cannot be fully fixed via
software update. The updated kernel packages provide software mitigation
for this hardware issue at a cost of potential performance penalty.
In this update initial mitigations for IBM Power (PowerPC) and IBM zSeries
(S390) architectures are provided.
* Variant CVE-2017-5715 triggers the speculative execution by utilizing
branch target injection. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
and guest/host boundaries and read privileged memory by conducting targeted
cache side-channel attacks. This fix specifically addresses S390
processors. (CVE-2017-5715, Important)
* Variant CVE-2017-5753 triggers the speculative execution by performing a
bounds-check bypass. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
boundary and read privileged memory by conducting targeted cache
side-channel attacks. This fix specifically addresses S390 and PowerPC
processors. (CVE-2017-5753, Important)
* Variant CVE-2017-5754 relies on the fact that, on impacted
microprocessors, during speculative execution of instruction permission
faults, exception generation triggered by a faulting access is suppressed
until the retirement of the whole instruction block. In a combination with
the fact that memory accesses may populate the cache even when the block is
being dropped and never committed (executed), an unprivileged local
attacker could use this flaw to read privileged (kernel space) memory by
conducting targeted cache side-channel attacks. Note: CVE-2017-5754 affects
Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected
by this issue. This fix specifically addresses PowerPC processors.
(CVE-2017-5754, Important)
Red Hat would like to thank Google Project Zero for reporting
CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754.
This update also fixes the following security issues and bugs:
Space precludes documenting all of the bug fixes and enhancements included
in this advisory. To see the complete list of bug fixes and enhancements,
refer to the following KnowledgeBase article:
https://access.redhat.com/articles/3327131.
4. Solution:
For details on how to apply this update, which includes the changes
described in this advisory, refer to:
https://access.redhat.com/articles/11258
The system must be rebooted for this update to take effect.
5. Bugs fixed (https://bugzilla.redhat.com/):
1284450 - CVE-2015-8539 kernel: local privesc in key management
1442086 - CVE-2017-7472 kernel: keyctl_set_reqkey_keyring() leaks thread keyrings
1493435 - CVE-2017-12192 kernel: NULL pointer dereference due to KEYCTL_READ on negative key
1501215 - CVE-2017-12193 kernel: Null pointer dereference due to incorrect node-splitting in assoc_array implementation
1504574 - CVE-2017-15649 kernel: Use-after-free in the af_packet.c
1519778 - CVE-2017-5753 hw: cpu: speculative execution bounds-check bypass
1519780 - CVE-2017-5715 hw: cpu: speculative execution branch target injection
1519781 - CVE-2017-5754 hw: cpu: speculative execution permission faults handling
6. Package List:
Red Hat Enterprise Linux Client (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Client Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux ComputeNode (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux ComputeNode Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Server (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
ppc64:
kernel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-bootwrapper-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-common-ppc64-3.10.0-693.17.1.el7.ppc64.rpm
kernel-devel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-headers-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.ppc64.rpm
perf-3.10.0-693.17.1.el7.ppc64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
ppc64le:
kernel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-bootwrapper-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-common-ppc64le-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-devel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-headers-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.ppc64le.rpm
perf-3.10.0-693.17.1.el7.ppc64le.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
s390x:
kernel-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.s390x.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-debuginfo-common-s390x-3.10.0-693.17.1.el7.s390x.rpm
kernel-devel-3.10.0-693.17.1.el7.s390x.rpm
kernel-headers-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-devel-3.10.0-693.17.1.el7.s390x.rpm
perf-3.10.0-693.17.1.el7.s390x.rpm
perf-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
python-perf-3.10.0-693.17.1.el7.s390x.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Server Optional (v. 7):
ppc64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-common-ppc64-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.ppc64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
ppc64le:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-common-ppc64le-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.ppc64le.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Workstation (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Workstation Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/
7. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2018 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFaab47XlSAg2UNWIIRAgi2AKDDW6z/9di3aoNQMX6PaIOzYTu39gCgncrF
n+VQu/CVEmiUW8aXZCnplaM=
=Km2i
-----END PGP SIGNATURE-----
--
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce
. Relevant releases/architectures:
Image Updates for RHV-H - noarch
Management Agent for RHEL 7 Hosts - noarch
3. Description:
The RHV-M Virtual Appliance automates the process of installing and
configuring the Red Hat Virtualization Manager. The appliance is available
to download as an OVA file from the Customer Portal.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
=============================================================================
FreeBSD-SA-18:03.speculative_execution Security Advisory
The FreeBSD Project
Topic: Speculative Execution Vulnerabilities
Category: core
Module: kernel
Announced: 2018-03-14
Credits: Jann Horn (Google Project Zero); Werner Haas, Thomas
Prescher (Cyberus Technology); Daniel Gruss, Moritz Lipp,
Stefan Mangard, Michael Schwarz (Graz University of
Technology); Paul Kocher; Daniel Genkin (University of
Pennsylvania and University of Maryland), Mike Hamburg
(Rambus); Yuval Yarom (University of Adelaide and Data6)
Affects: All supported versions of FreeBSD.
Corrected: 2018-02-17 18:00:01 UTC (stable/11, 11.1-STABLE)
2018-03-14 04:00:00 UTC (releng/11.1, 11.1-RELEASE-p8)
CVE Name: CVE-2017-5715, CVE-2017-5754
Special Note: Speculative execution vulnerability mitigation is a work
in progress. This advisory addresses the most significant
issues for FreeBSD 11.1 on amd64 CPUs. We expect to update
this advisory to include 10.x for amd64 CPUs. Future FreeBSD
releases will address this issue on i386 and other CPUs.
freebsd-update will include changes on i386 as part of this
update due to common code changes shared between amd64 and
i386, however it contains no functional changes for i386 (in
particular, it does not mitigate the issue on i386).
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:https://security.FreeBSD.org/>.
II. Problem Description
A number of issues relating to speculative execution were found last year
and publicly announced January 3rd. Two of these, known as Meltdown and
Spectre V2, are addressed here.
CVE-2017-5754 (Meltdown)
- ------------------------
This issue relies on an affected CPU speculatively executing instructions
beyond a faulting instruction. When this happens, changes to architectural
state are not committed, but observable changes may be left in micro-
architectural state (for example, cache). This may be used to infer
privileged data.
CVE-2017-5715 (Spectre V2)
- --------------------------
Spectre V2 uses branch target injection to speculatively execute kernel code
at an address under the control of an attacker.
III. Impact
An attacker may be able to read secret data from the kernel or from a
process when executing untrusted code (for example, in a web browser).
IV. Workaround
No workaround is available.
V. Solution
Perform one of the following:
1) Upgrade your vulnerable system to a supported FreeBSD stable or
release / security branch (releng) dated after the correction date,
and reboot.
2) To update your vulnerable system via a binary patch:
Systems running a RELEASE version of FreeBSD on the i386 or amd64
platforms can be updated via the freebsd-update(8) utility, followed
by a reboot into the new kernel:
# freebsd-update fetch
# freebsd-update install
# shutdown -r now
3) To update your vulnerable system via a source code patch:
The following patches have been verified to apply to the applicable
FreeBSD release branches.
a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.
[FreeBSD 11.1]
# fetch https://security.FreeBSD.org/patches/SA-18:03/speculative_execution-amd64-11.patch
# fetch https://security.FreeBSD.org/patches/SA-18:03/speculative_execution-amd64-11.patch.asc
# gpg --verify speculative_execution-amd64-11.patch.asc
b) Apply the patch. Execute the following commands as root:
# cd /usr/src
# patch < /path/to/patch
c) Recompile your kernel as described in
<URL:https://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.
VI. Correction details
CVE-2017-5754 (Meltdown)
- ------------------------
The mitigation is known as Page Table Isolation (PTI). PTI largely separates
kernel and user mode page tables, so that even during speculative execution
most of the kernel's data is unmapped and not accessible. A positive result is definitive
(that is, the vulnerability exists with certainty). A negative result
indicates either that the CPU is not affected, or that the test is not
capable of demonstrating the issue on the CPU (and may need to be modified).
A patched kernel will automatically enable PTI on Intel CPUs. The status can
be checked via the vm.pmap.pti sysctl:
# sysctl vm.pmap.pti
vm.pmap.pti: 1
The default setting can be overridden by setting the loader tunable
vm.pmap.pti to 1 or 0 in /boot/loader.conf. This setting takes effect only
at boot.
PTI introduces a performance regression. The observed performance loss is
significant in microbenchmarks of system call overhead, but is much smaller
for many real workloads.
CVE-2017-5715 (Spectre V2)
- --------------------------
There are two common mitigations for Spectre V2. This patch includes a
mitigation using Indirect Branch Restricted Speculation, a feature available
via a microcode update from processor manufacturers. The alternate
mitigation, Retpoline, is a feature available in newer compilers. The
feasibility of applying Retpoline to stable branches and/or releases is under
investigation.
The patch includes the IBRS mitigation for Spectre V2. To use the mitigation
the system must have an updated microcode; with older microcode a patched
kernel will function without the mitigation.
IBRS can be disabled via the hw.ibrs_disable sysctl (and tunable), and the
status can be checked via the hw.ibrs_active sysctl. IBRS may be enabled or
disabled at runtime. Additional detail on microcode updates will follow.
The following list contains the correction revision numbers for each
affected branch.
Branch/path Revision
- -------------------------------------------------------------------------
stable/11/ r329462
releng/11.1/ r330908
- -------------------------------------------------------------------------
To see which files were modified by a particular revision, run the
following command, replacing NNNNNN with the revision number, on a
machine with Subversion installed:
# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base
Or visit the following URL, replacing NNNNNN with the revision number:
<URL:https://svnweb.freebsd.org/base?view=revision&revision=NNNNNN>
VII. 6.7) - i386, ppc64, s390x, x86_64
3. (BZ#1554253)
4. ==========================================================================
Ubuntu Security Notice USN-3583-1
February 23, 2018
linux vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
Details:
It was discovered that an out-of-bounds write vulnerability existed in the
Flash-Friendly File System (f2fs) in the Linux kernel. An attacker could
construct a malicious file system that, when mounted, could cause a denial
of service (system crash) or possibly execute arbitrary code.
(CVE-2017-0750)
It was discovered that a race condition leading to a use-after-free
vulnerability existed in the ALSA PCM subsystem of the Linux kernel. A
local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2017-0861)
It was discovered that the KVM implementation in the Linux kernel allowed
passthrough of the diagnostic I/O port 0x80. An attacker in a guest VM
could use this to cause a denial of service (system crash) in the host OS.
(CVE-2017-1000407)
Bo Zhang discovered that the netlink wireless configuration interface in
the Linux kernel did not properly validate attributes when handling certain
requests. A local attacker with the CAP_NET_ADMIN could use this to cause a
denial of service (system crash). (CVE-2017-12153)
Vitaly Mayatskikh discovered that the SCSI subsystem in the Linux kernel
did not properly track reference counts when merging buffers. A local
attacker could use this to cause a denial of service (memory exhaustion).
(CVE-2017-12190)
It was discovered that the key management subsystem in the Linux kernel did
not properly restrict key reads on negatively instantiated keys. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2017-12192)
It was discovered that an integer overflow existed in the sysfs interface
for the QLogic 24xx+ series SCSI driver in the Linux kernel. A local
privileged attacker could use this to cause a denial of service (system
crash). (CVE-2017-14051)
Otto Ebeling discovered that the memory manager in the Linux kernel did not
properly check the effective UID in some situations. A local attacker could
use this to expose sensitive information. (CVE-2017-14140)
It was discovered that the ATI Radeon framebuffer driver in the Linux
kernel did not properly initialize a data structure returned to user space. (CVE-2017-14156)
ChunYu Wang discovered that the iSCSI transport implementation in the Linux
kernel did not properly validate data structures. A local attacker could
use this to cause a denial of service (system crash). (CVE-2017-14489)
James Patrick-Evans discovered a race condition in the LEGO USB Infrared
Tower driver in the Linux kernel. A physically proximate attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2017-15102)
ChunYu Wang discovered that a use-after-free vulnerability existed in the
SCTP protocol implementation in the Linux kernel. A local attacker could
use this to cause a denial of service (system crash) or possibly execute
arbitrary code, (CVE-2017-15115)
It was discovered that the key management subsystem in the Linux kernel did
not properly handle NULL payloads with non-zero length values. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2017-15274)
It was discovered that the Bluebooth Network Encapsulation Protocol (BNEP)
implementation in the Linux kernel did not validate the type of socket
passed in the BNEPCONNADD ioctl(). A local attacker with the CAP_NET_ADMIN
privilege could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2017-15868)
Andrey Konovalov discovered a use-after-free vulnerability in the USB
serial console driver in the Linux kernel. A physically proximate attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2017-16525)
It was discovered that the netfilter passive OS fingerprinting (xt_osf)
module did not properly perform access control checks. A local attacker
could improperly modify the systemwide OS fingerprint list.
(CVE-2017-17450)
It was discovered that the HMAC implementation did not validate the state
of the underlying cryptographic hash algorithm. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2017-17806)
Denys Fedoryshchenko discovered a use-after-free vulnerability in the
netfilter xt_TCPMSS filter of the Linux kernel. A remote attacker could use
this to cause a denial of service (system crash). (CVE-2017-18017)
Gareth Evans discovered that the shm IPC subsystem in the Linux kernel did
not properly restrict mapping page zero. A local privileged attacker could
use this to execute arbitrary code. (CVE-2017-5669)
It was discovered that an integer overflow vulnerability existing in the
IPv6 implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (infinite loop). (CVE-2017-7542)
Tommi Rantala and Brad Spengler discovered that the memory manager in the
Linux kernel did not properly enforce the CONFIG_STRICT_DEVMEM protection
mechanism. A local attacker with access to /dev/mem could use this to
expose sensitive information or possibly execute arbitrary code.
(CVE-2017-7889)
Mohamed Ghannam discovered a use-after-free vulnerability in the DCCP
protocol implementation in the Linux kernel. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2017-8824)
Mohamed Ghannam discovered a null pointer dereference in the RDS (Reliable
Datagram Sockets) protocol implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2018-5333)
ee3/4ePS discovered that a race condition existed in loop block device
implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5344)
USN-3524-1 mitigated CVE-2017-5754 (Meltdown) for the amd64
architecture in Ubuntu 14.04 LTS. This update provides the
corresponding mitigations for the ppc64el architecture. This flaw is known as Meltdown.
(CVE-2017-5754)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-3.13.0-142-generic 3.13.0-142.191
linux-image-3.13.0-142-generic-lpae 3.13.0-142.191
linux-image-3.13.0-142-lowlatency 3.13.0-142.191
linux-image-3.13.0-142-powerpc-e500 3.13.0-142.191
linux-image-3.13.0-142-powerpc-e500mc 3.13.0-142.191
linux-image-3.13.0-142-powerpc-smp 3.13.0-142.191
linux-image-3.13.0-142-powerpc64-emb 3.13.0-142.191
linux-image-3.13.0-142-powerpc64-smp 3.13.0-142.191
linux-image-generic 3.13.0.142.152
linux-image-generic-lpae 3.13.0.142.152
linux-image-lowlatency 3.13.0.142.152
linux-image-powerpc-e500 3.13.0.142.152
linux-image-powerpc-e500mc 3.13.0.142.152
linux-image-powerpc-smp 3.13.0.142.152
linux-image-powerpc64-emb 3.13.0.142.152
linux-image-powerpc64-smp 3.13.0.142.152
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3583-1
CVE-2017-0750, CVE-2017-0861, CVE-2017-1000407, CVE-2017-12153,
CVE-2017-12190, CVE-2017-12192, CVE-2017-14051, CVE-2017-14140,
CVE-2017-14156, CVE-2017-14489, CVE-2017-15102, CVE-2017-15115,
CVE-2017-15274, CVE-2017-15868, CVE-2017-16525, CVE-2017-17450,
CVE-2017-17806, CVE-2017-18017, CVE-2017-5669, CVE-2017-5754,
CVE-2017-7542, CVE-2017-7889, CVE-2017-8824, CVE-2018-5333,
CVE-2018-5344
Package Information:
https://launchpad.net/ubuntu/+source/linux/3.13.0-142.191
| VAR-201801-0826 | CVE-2017-5715 | CPU hardware utilizing speculative execution may be vulnerable to cache side-channel attacks |
CVSS V2: 1.9 CVSS V3: 5.6 Severity: MEDIUM |
Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. CPU hardware utilizing speculative execution may be vulnerable to cache timing side-channel analysis. Two vulnerabilities are identified, known as "Variant 3a" and "Variant 4". CPUhardware is a set of firmware that runs in the CPU (Central Processing Unit) for managing and controlling the CPU. The Meltdown vulnerability exists in the CPU processor core, which \"melts\" the security boundary implemented by hardware, allowing low-privileged user-level applications to \"cross-border\" access to system-level memory, causing data leakage. The following products and versions are affected: ARM Cortex-R7; Cortex-R8; Cortex-A8; Cortex-A9; Cortex-A12; Intel Xeon CPU E5-1650 v3, v2, v4 versions; Xeon E3-1265l v2, v3, v4 Version; Xeon E3-1245 v2, v3, v5, v6 versions; Xeon X7542, etc. Relevant releases/architectures:
Image Updates for RHV-H - noarch
3. These
packages include redhat-release-virtualization-host, ovirt-node, and
rhev-hypervisor. RHVH features a Cockpit user interface for
monitoring the host's resources and performing administrative tasks. ==========================================================================
Ubuntu Security Notice USN-3582-1
February 22, 2018
linux, linux-aws, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel. A local attacker could use this to cause a denial of service or
possibly execute arbitrary code. (CVE-2017-17712)
Laurent Guerby discovered that the mbcache feature in the ext2 and ext4
filesystems in the Linux kernel improperly handled xattr block caching. A
local attacker could use this to cause a denial of service. (CVE-2015-8952)
Vitaly Mayatskikh discovered that the SCSI subsystem in the Linux kernel
did not properly track reference counts when merging buffers. A local
attacker could use this to cause a denial of service (memory exhaustion).
(CVE-2017-12190)
ChunYu Wang discovered that a use-after-free vulnerability existed in the
SCTP protocol implementation in the Linux kernel. A local attacker could
use this to cause a denial of service (system crash) or possibly execute
arbitrary code, (CVE-2017-15115)
Mohamed Ghannam discovered a use-after-free vulnerability in the DCCP
protocol implementation in the Linux kernel. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2017-8824)
USN-3540-1 mitigated CVE-2017-5715 (Spectre Variant 2) for the
amd64 architecture in Ubuntu 16.04 LTS. This update provides the
compiler-based retpoline kernel mitigation for the amd64 and i386
architectures. This flaw is known as Spectre. A local attacker could use this to
expose sensitive information, including kernel memory.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well. 7) - aarch64, noarch, ppc64le
3. (CVE-2018-3639, PowerPC)
* This release also includes next iteration of the CVE-2017-5715 mitigation
that includes the SMCCC (Secure Monitor Call Calling Convention) 1.1
support. See the
descriptions in the related Knowledge Article:
https://access.redhat.com/articles/3485851
4. 6) - i386, x86_64
3. Description:
Kernel-based Virtual Machine (KVM) is a full virtualization solution for
Linux on a variety of architectures. The qemu-kvm package provides the
user-space component for running virtual machines that use KVM. (CVE-2017-5715)
Note: This is the qemu-kvm side of the CVE-2017-5715 mitigation. Once
all virtual machines have shut down, start them again for this update to
take effect.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=====================================================================
Red Hat Security Advisory
Synopsis: Important: kernel security and bug fix update
Advisory ID: RHSA-2018:0151-01
Product: Red Hat Enterprise Linux
Advisory URL: https://access.redhat.com/errata/RHSA-2018:0151
Issue date: 2018-01-25
CVE Names: CVE-2015-8539 CVE-2017-7472 CVE-2017-12192
CVE-2017-12193 CVE-2017-15649
=====================================================================
1. Summary:
An update for kernel is now available for Red Hat Enterprise Linux 7.
Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.
2. Relevant releases/architectures:
Red Hat Enterprise Linux Client (v. 7) - noarch, x86_64
Red Hat Enterprise Linux Client Optional (v. 7) - x86_64
Red Hat Enterprise Linux ComputeNode (v. 7) - noarch, x86_64
Red Hat Enterprise Linux ComputeNode Optional (v. 7) - x86_64
Red Hat Enterprise Linux Server (v. 7) - noarch, ppc64, ppc64le, s390x, x86_64
Red Hat Enterprise Linux Server Optional (v. 7) - ppc64, ppc64le, x86_64
Red Hat Enterprise Linux Workstation (v. 7) - noarch, x86_64
Red Hat Enterprise Linux Workstation Optional (v. 7) - x86_64
3. Description:
The kernel packages contain the Linux kernel, the core of any Linux
operating system.
Security Fix(es):
An industry-wide issue was found in the way many modern microprocessor
designs have implemented speculative execution of instructions (a commonly
used performance optimization). There are three primary variants of the
issue which differ in the way the speculative execution can be exploited.
Note: This issue is present in hardware and cannot be fully fixed via
software update. The updated kernel packages provide software mitigation
for this hardware issue at a cost of potential performance penalty. Please
refer to References section for further information about this issue and
the performance impact.
In this update initial mitigations for IBM Power (PowerPC) and IBM zSeries
(S390) architectures are provided.
* Variant CVE-2017-5715 triggers the speculative execution by utilizing
branch target injection. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
and guest/host boundaries and read privileged memory by conducting targeted
cache side-channel attacks. This fix specifically addresses S390
processors. (CVE-2017-5715, Important)
* Variant CVE-2017-5753 triggers the speculative execution by performing a
bounds-check bypass. It relies on the presence of a precisely-defined
instruction sequence in the privileged code as well as the fact that memory
accesses may cause allocation into the microprocessor's data cache even for
speculatively executed instructions that never actually commit (retire). As
a result, an unprivileged attacker could use this flaw to cross the syscall
boundary and read privileged memory by conducting targeted cache
side-channel attacks. This fix specifically addresses S390 and PowerPC
processors. (CVE-2017-5753, Important)
* Variant CVE-2017-5754 relies on the fact that, on impacted
microprocessors, during speculative execution of instruction permission
faults, exception generation triggered by a faulting access is suppressed
until the retirement of the whole instruction block. In a combination with
the fact that memory accesses may populate the cache even when the block is
being dropped and never committed (executed), an unprivileged local
attacker could use this flaw to read privileged (kernel space) memory by
conducting targeted cache side-channel attacks. Note: CVE-2017-5754 affects
Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected
by this issue. This fix specifically addresses PowerPC processors.
(CVE-2017-5754, Important)
Red Hat would like to thank Google Project Zero for reporting
CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754.
This update also fixes the following security issues and bugs:
Space precludes documenting all of the bug fixes and enhancements included
in this advisory. To see the complete list of bug fixes and enhancements,
refer to the following KnowledgeBase article:
https://access.redhat.com/articles/3327131.
4. Solution:
For details on how to apply this update, which includes the changes
described in this advisory, refer to:
https://access.redhat.com/articles/11258
The system must be rebooted for this update to take effect.
5. Bugs fixed (https://bugzilla.redhat.com/):
1284450 - CVE-2015-8539 kernel: local privesc in key management
1442086 - CVE-2017-7472 kernel: keyctl_set_reqkey_keyring() leaks thread keyrings
1493435 - CVE-2017-12192 kernel: NULL pointer dereference due to KEYCTL_READ on negative key
1501215 - CVE-2017-12193 kernel: Null pointer dereference due to incorrect node-splitting in assoc_array implementation
1504574 - CVE-2017-15649 kernel: Use-after-free in the af_packet.c
1519778 - CVE-2017-5753 hw: cpu: speculative execution bounds-check bypass
1519780 - CVE-2017-5715 hw: cpu: speculative execution branch target injection
1519781 - CVE-2017-5754 hw: cpu: speculative execution permission faults handling
6. Package List:
Red Hat Enterprise Linux Client (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Client Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux ComputeNode (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux ComputeNode Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Server (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
ppc64:
kernel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-bootwrapper-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-common-ppc64-3.10.0-693.17.1.el7.ppc64.rpm
kernel-devel-3.10.0-693.17.1.el7.ppc64.rpm
kernel-headers-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.ppc64.rpm
perf-3.10.0-693.17.1.el7.ppc64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
ppc64le:
kernel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-bootwrapper-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-common-ppc64le-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-devel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-headers-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.ppc64le.rpm
perf-3.10.0-693.17.1.el7.ppc64le.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
s390x:
kernel-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.s390x.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-debuginfo-common-s390x-3.10.0-693.17.1.el7.s390x.rpm
kernel-devel-3.10.0-693.17.1.el7.s390x.rpm
kernel-headers-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
kernel-kdump-devel-3.10.0-693.17.1.el7.s390x.rpm
perf-3.10.0-693.17.1.el7.s390x.rpm
perf-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
python-perf-3.10.0-693.17.1.el7.s390x.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.s390x.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Server Optional (v. 7):
ppc64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-debuginfo-common-ppc64-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.ppc64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64.rpm
ppc64le:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-debuginfo-common-ppc64le-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.ppc64le.rpm
perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.ppc64le.rpm
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Workstation (v. 7):
Source:
kernel-3.10.0-693.17.1.el7.src.rpm
noarch:
kernel-abi-whitelists-3.10.0-693.17.1.el7.noarch.rpm
kernel-doc-3.10.0-693.17.1.el7.noarch.rpm
x86_64:
kernel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debug-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-devel-3.10.0-693.17.1.el7.x86_64.rpm
kernel-headers-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-3.10.0-693.17.1.el7.x86_64.rpm
perf-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
Red Hat Enterprise Linux Workstation Optional (v. 7):
x86_64:
kernel-debug-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-debuginfo-common-x86_64-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
kernel-tools-libs-devel-3.10.0-693.17.1.el7.x86_64.rpm
perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
python-perf-debuginfo-3.10.0-693.17.1.el7.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/
7. References:
https://access.redhat.com/security/cve/CVE-2015-8539
https://access.redhat.com/security/cve/CVE-2017-7472
https://access.redhat.com/security/cve/CVE-2017-12192
https://access.redhat.com/security/cve/CVE-2017-12193
https://access.redhat.com/security/cve/CVE-2017-15649
https://access.redhat.com/security/updates/classification/#important
https://access.redhat.com/security/vulnerabilities/speculativeexecution
https://access.redhat.com/security/cve/CVE-2017-5753
https://access.redhat.com/security/cve/CVE-2017-5715
https://access.redhat.com/security/cve/CVE-2017-5754
https://access.redhat.com/articles/3327131
8. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2018 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFaab47XlSAg2UNWIIRAgi2AKDDW6z/9di3aoNQMX6PaIOzYTu39gCgncrF
n+VQu/CVEmiUW8aXZCnplaM=
=Km2i
-----END PGP SIGNATURE-----
--
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce
.
This update allows libvirt to expose new CPU features added by microcode
updates to guests. On amd64 and i386, new CPU models that match the updated
microcode features were added with an -IBRS suffix. Certain environments
will require guests to be switched manually to the new CPU models after
microcode updates have been applied to the host. Description:
The libvirt library contains a C API for managing and interacting with the
virtualization capabilities of Linux and other operating systems. In
addition, libvirt provides tools for remote management of virtualized
systems. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201804-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: QEMU: Multiple vulnerabilities
Date: April 08, 2018
Bugs: #629348, #638506, #643432, #646814, #649616
ID: 201804-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in QEMU, the worst of which
may allow an attacker to execute arbitrary code.
Background
==========
QEMU is a generic and open source machine emulator and virtualizer.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-emulation/qemu < 2.11.1-r1 >= 2.11.1-r1
Description
===========
Multiple vulnerabilities have been discovered in QEMU. Please review
the CVE identifiers referenced below for details.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All QEMU users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-emulation/qemu-2.11.1-r1"
References
==========
[ 1 ] CVE-2017-13672
https://nvd.nist.gov/vuln/detail/CVE-2017-13672
[ 2 ] CVE-2017-15124
https://nvd.nist.gov/vuln/detail/CVE-2017-15124
[ 3 ] CVE-2017-16845
https://nvd.nist.gov/vuln/detail/CVE-2017-16845
[ 4 ] CVE-2017-17381
https://nvd.nist.gov/vuln/detail/CVE-2017-17381
[ 5 ] CVE-2017-18030
https://nvd.nist.gov/vuln/detail/CVE-2017-18030
[ 6 ] CVE-2017-18043
https://nvd.nist.gov/vuln/detail/CVE-2017-18043
[ 7 ] CVE-2017-5715
https://nvd.nist.gov/vuln/detail/CVE-2017-5715
[ 8 ] CVE-2018-5683
https://nvd.nist.gov/vuln/detail/CVE-2018-5683
[ 9 ] CVE-2018-5748
https://nvd.nist.gov/vuln/detail/CVE-2018-5748
[ 10 ] CVE-2018-7550
https://nvd.nist.gov/vuln/detail/CVE-2018-7550
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201804-08
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2018 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
| VAR-201801-1063 | CVE-2018-0114 | Cisco node-jose Vulnerability related to key management errors in open source libraries |
CVSS V2: 5.0 CVSS V3: 7.5 Severity: HIGH |
A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header. Cisco Node-jose Library is prone to a remote security-bypass vulnerability.
Attackers can exploit this issue to bypass certain security restrictions to gain unauthorized access. This may aid in further attacks
| VAR-201801-1055 | CVE-2018-0104 | Cisco WebEx Network Recording Player Input validation vulnerability |
CVSS V2: 9.3 CVSS V3: 9.6 Severity: CRITICAL |
A vulnerability in Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) files could allow a remote attacker to execute arbitrary code on the system of a targeted user. The attacker could exploit this vulnerability by sending the user a link or email attachment with a malicious ARF file and persuading the user to follow the link or launch the file. Successful exploitation could allow the attacker to execute arbitrary code on the user's system. This vulnerability affects Cisco WebEx Business Suite meeting sites, Cisco WebEx Meetings sites, Cisco WebEx Meetings Server, and Cisco WebEx ARF players. Cisco Bug IDs: CSCvg78853, CSCvg78856, CSCvg78857. Vendors have confirmed this vulnerability Bug ID CSCvg78853 , CSCvg78856 ,and CSCvg78857 It is released as.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. While opening an ARF file, WebEx Network Recording Player loads a DLL from an unqualified path
| VAR-201801-0212 | CVE-2017-1612 | IBM WebSphere MQ Vulnerabilities related to authorization, permissions, and access control |
CVSS V2: 4.6 CVSS V3: 7.8 Severity: HIGH |
IBM WebSphere MQ 7.0, 7.1, 7.5, 8.0, and 9.0 service trace module could be used to execute untrusted code under 'mqm' user. IBM X-Force ID: 132953. Vendors have confirmed this vulnerability IBM X-Force ID: 132953 It is released as.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. IBM WebSphere MQ is prone to a local privilege-escalation vulnerability.
Successfully exploiting this issue may allow an attacker to execute arbitrary code with elevated privileges
| VAR-201801-0296 | CVE-2017-1000471 | EmbedThis GoAhead Webserver In NULL Pointer dereference vulnerability |
CVSS V2: 7.5 CVSS V3: 9.8 Severity: CRITICAL |
EmbedThis GoAhead Webserver version 4.0.0 is vulnerable to a NULL pointer dereference in the CGI handler resulting in memory corruption or denial of service. Embedthis Goahead Webserver is a small and exquisite embedded Web server of American Embedthis Software Company, which supports embedding in various devices and applications. CGI handler is one of the CGI handlers
| VAR-201801-1054 | CVE-2018-0103 | Cisco WebEx Network Recording Player Buffer error vulnerability |
CVSS V2: 9.3 CVSS V3: 7.8 Severity: HIGH |
A Buffer Overflow vulnerability in Cisco WebEx Network Recording Player for Advanced Recording Format (ARF) files could allow a local attacker to execute arbitrary code on the system of a user. The attacker could exploit this vulnerability by sending the user a link or email attachment with a malicious ARF file and persuading the user to follow the link or launch the file. Successful exploitation could allow the attacker to execute arbitrary code on the user's system. This vulnerability affects Cisco WebEx Business Suite meeting sites, Cisco WebEx Meetings sites, Cisco WebEx Meetings Server, and Cisco WebEx ARF players. Cisco Bug IDs: CSCvg78835, CSCvg78837, CSCvg78839. Vendors have confirmed this vulnerability Bug ID CSCvg78835 , CSCvg78837 ,and CSCvg78839 It is released as.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. Crafted data in an ARF file can trigger an overflow of a heap-based buffer.
Attackers can exploit this issue to cause a denial-of-service condition. WebEx ARF player is one of the media players mainly used to play WebEx recording files in ARF format
| VAR-201801-1708 | CVE-2017-18017 | Linux Kernel Uses freed memory vulnerability |
CVSS V2: 10.0 CVSS V3: 9.8 Severity: CRITICAL |
The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action. Linux Kernel Contains a vulnerability in the use of freed memory.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. Linux Kernel is prone to a denial-of-service vulnerability.
An attacker can exploit this issue to cause a denial-of-service condition.
Linux kernel versions prior to 4.11, and 4.9.x prior to 4.9.36 are vulnerable. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=====================================================================
Red Hat Security Advisory
Synopsis: Important: kernel security and bug fix update
Advisory ID: RHSA-2018:1319-01
Product: Red Hat Enterprise Linux
Advisory URL: https://access.redhat.com/errata/RHSA-2018:1319
Issue date: 2018-05-08
CVE Names: CVE-2017-7645 CVE-2017-8824 CVE-2017-13166
CVE-2017-18017 CVE-2017-1000410 CVE-2018-8897
=====================================================================
1. Summary:
An update for kernel is now available for Red Hat Enterprise Linux 6.
Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.
2. Relevant releases/architectures:
Red Hat Enterprise Linux Desktop (v. 6) - i386, noarch, x86_64
Red Hat Enterprise Linux Desktop Optional (v. 6) - i386, x86_64
Red Hat Enterprise Linux HPC Node (v. 6) - noarch, x86_64
Red Hat Enterprise Linux HPC Node Optional (v. 6) - x86_64
Red Hat Enterprise Linux Server (v. 6) - i386, noarch, ppc64, s390x, x86_64
Red Hat Enterprise Linux Server Optional (v. 6) - i386, ppc64, s390x, x86_64
Red Hat Enterprise Linux Workstation (v. 6) - i386, noarch, x86_64
Red Hat Enterprise Linux Workstation Optional (v. 6) - i386, x86_64
3.
Security Fix(es):
* hw: cpu: speculative execution permission faults handling (CVE-2017-5754)
* Kernel: error in exception handling leads to DoS (CVE-2018-8897)
* kernel: nfsd: Incorrect handling of long RPC replies (CVE-2017-7645)
* kernel: Use-after-free vulnerability in DCCP socket (CVE-2017-8824)
* kernel: v4l2: disabled memory access protection mechanism allowing
privilege escalation (CVE-2017-13166)
* kernel: netfilter: use-after-free in tcpmss_mangle_packet function in
net/netfilter/xt_TCPMSS.c (CVE-2017-18017)
* kernel: Stack information leak in the EFS element (CVE-2017-1000410)
For more details about the security issue(s), including the impact, a CVSS
score, and other related information, refer to the CVE page(s) listed in
the References section.
Red Hat would like to thank Google Project Zero for reporting
CVE-2017-5754; Nick Peterson (Everdox Tech LLC) and Andy Lutomirski for
reporting CVE-2018-8897; Mohamed Ghannam for reporting CVE-2017-8824; and
Armis Labs for reporting CVE-2017-1000410.
Bug Fix(es):
These updated kernel packages include also numerous bug fixes. Space
precludes documenting all of these bug fixes in this advisory. See the bug
fix descriptions in the related Knowledge Article:
https://access.redhat.com/articles/3431591
4. Solution:
For details on how to apply this update, which includes the changes
described in this advisory, refer to:
https://access.redhat.com/articles/11258
The system must be rebooted for this update to take effect.
5. Bugs fixed (https://bugzilla.redhat.com/):
1443615 - CVE-2017-7645 kernel: nfsd: Incorrect handling of long RPC replies
1519160 - CVE-2017-1000410 kernel: Stack information leak in the EFS element
1519591 - CVE-2017-8824 kernel: Use-after-free vulnerability in DCCP socket
1519781 - CVE-2017-5754 hw: cpu: speculative execution permission faults handling
1531135 - CVE-2017-18017 kernel: netfilter: use-after-free in tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c
1548412 - CVE-2017-13166 kernel: v4l2: disabled memory access protection mechanism allowing privilege escalation
1567074 - CVE-2018-8897 Kernel: error in exception handling leads to DoS
6. Package List:
Red Hat Enterprise Linux Desktop (v. 6):
Source:
kernel-2.6.32-696.28.1.el6.src.rpm
i386:
kernel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-headers-2.6.32-696.28.1.el6.i686.rpm
perf-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.28.1.el6.noarch.rpm
kernel-doc-2.6.32-696.28.1.el6.noarch.rpm
kernel-firmware-2.6.32-696.28.1.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
kernel-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-headers-2.6.32-696.28.1.el6.x86_64.rpm
perf-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux Desktop Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux HPC Node (v. 6):
Source:
kernel-2.6.32-696.28.1.el6.src.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.28.1.el6.noarch.rpm
kernel-doc-2.6.32-696.28.1.el6.noarch.rpm
kernel-firmware-2.6.32-696.28.1.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
kernel-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-headers-2.6.32-696.28.1.el6.x86_64.rpm
perf-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux HPC Node Optional (v. 6):
x86_64:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux Server (v. 6):
Source:
kernel-2.6.32-696.28.1.el6.src.rpm
i386:
kernel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-headers-2.6.32-696.28.1.el6.i686.rpm
perf-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.28.1.el6.noarch.rpm
kernel-doc-2.6.32-696.28.1.el6.noarch.rpm
kernel-firmware-2.6.32-696.28.1.el6.noarch.rpm
ppc64:
kernel-2.6.32-696.28.1.el6.ppc64.rpm
kernel-bootwrapper-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debug-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debuginfo-common-ppc64-2.6.32-696.28.1.el6.ppc64.rpm
kernel-devel-2.6.32-696.28.1.el6.ppc64.rpm
kernel-headers-2.6.32-696.28.1.el6.ppc64.rpm
perf-2.6.32-696.28.1.el6.ppc64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
s390x:
kernel-2.6.32-696.28.1.el6.s390x.rpm
kernel-debug-2.6.32-696.28.1.el6.s390x.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.s390x.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
kernel-debuginfo-common-s390x-2.6.32-696.28.1.el6.s390x.rpm
kernel-devel-2.6.32-696.28.1.el6.s390x.rpm
kernel-headers-2.6.32-696.28.1.el6.s390x.rpm
kernel-kdump-2.6.32-696.28.1.el6.s390x.rpm
kernel-kdump-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
kernel-kdump-devel-2.6.32-696.28.1.el6.s390x.rpm
perf-2.6.32-696.28.1.el6.s390x.rpm
perf-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
x86_64:
kernel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
kernel-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-headers-2.6.32-696.28.1.el6.x86_64.rpm
perf-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux Server Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
ppc64:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
kernel-debuginfo-common-ppc64-2.6.32-696.28.1.el6.ppc64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
python-perf-2.6.32-696.28.1.el6.ppc64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.ppc64.rpm
s390x:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
kernel-debuginfo-common-s390x-2.6.32-696.28.1.el6.s390x.rpm
kernel-kdump-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
perf-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
python-perf-2.6.32-696.28.1.el6.s390x.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.s390x.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux Workstation (v. 6):
Source:
kernel-2.6.32-696.28.1.el6.src.rpm
i386:
kernel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-headers-2.6.32-696.28.1.el6.i686.rpm
perf-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
noarch:
kernel-abi-whitelists-2.6.32-696.28.1.el6.noarch.rpm
kernel-doc-2.6.32-696.28.1.el6.noarch.rpm
kernel-firmware-2.6.32-696.28.1.el6.noarch.rpm
x86_64:
kernel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.i686.rpm
kernel-debug-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
kernel-devel-2.6.32-696.28.1.el6.x86_64.rpm
kernel-headers-2.6.32-696.28.1.el6.x86_64.rpm
perf-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
Red Hat Enterprise Linux Workstation Optional (v. 6):
i386:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.i686.rpm
kernel-debuginfo-common-i686-2.6.32-696.28.1.el6.i686.rpm
perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
python-perf-2.6.32-696.28.1.el6.i686.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.i686.rpm
x86_64:
kernel-debug-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
kernel-debuginfo-common-x86_64-2.6.32-696.28.1.el6.x86_64.rpm
perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-2.6.32-696.28.1.el6.x86_64.rpm
python-perf-debuginfo-2.6.32-696.28.1.el6.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/
7. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2018 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFa8fO8XlSAg2UNWIIRAnN0AKCBdjdw1bC12xju0GwoOedA1L8osACaA1Ze
4IKrbiFeHd+C9bqCjUFX4pw=
=3psi
-----END PGP SIGNATURE-----
--
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce
.
Security Fix(es):
* An industry-wide issue was found in the way many modern microprocessor
designs have implemented speculative execution of Load & Store instructions
(a commonly used performance optimization). It relies on the presence of a
precisely-defined instruction sequence in the privileged code as well as
the fact that memory read from address to which a recent memory write has
occurred may see an older value and subsequently cause an update into the
microprocessor's data cache even for speculatively executed instructions
that never actually commit (retire). As a result, an unprivileged attacker
could use this flaw to read privileged memory by conducting targeted cache
side-channel attacks. (CVE-2018-3639)
Note: This issue is present in hardware and cannot be fully fixed via
software update. To be fully functional, up-to-date CPU
microcode applied on the system might be required. Please refer to
References section for further information about this issue, CPU microcode
requirements and the potential performance impact. Bugs fixed (https://bugzilla.redhat.com/):
1531135 - CVE-2017-18017 kernel: netfilter: use-after-free in tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c
1566890 - CVE-2018-3639 hw: cpu: speculative store bypass
6. (BZ#1549731)
* Intel Core X-Series (Skylake) processors use a hardcoded Time Stamp
Counter (TSC) frequency of 25 MHz. In some cases this can be imprecise and
lead to timing-related problems such as time drift, timers being triggered
early, or TSC clock instability. This update mitigates these problems by no
longer using the "native_calibrate_tsc()" function to define the TSC
frequency. Refined calibration is now used to update the clock rate
accordingly in these cases. (BZ#1547854)
4. 7) - noarch, x86_64
3. Description:
The kernel-rt packages provide the Real Time Linux Kernel, which enables
fine-tuning for systems with extremely high determinism requirements. SchAPnherr (Amazon) for reporting CVE-2017-1000252; and Armis Labs
for reporting CVE-2017-1000410. ==========================================================================
Ubuntu Security Notice USN-3583-1
February 23, 2018
linux vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel. An attacker could
construct a malicious file system that, when mounted, could cause a denial
of service (system crash) or possibly execute arbitrary code.
(CVE-2017-0750)
It was discovered that a race condition leading to a use-after-free
vulnerability existed in the ALSA PCM subsystem of the Linux kernel. A
local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2017-0861)
It was discovered that the KVM implementation in the Linux kernel allowed
passthrough of the diagnostic I/O port 0x80. An attacker in a guest VM
could use this to cause a denial of service (system crash) in the host OS.
(CVE-2017-1000407)
Bo Zhang discovered that the netlink wireless configuration interface in
the Linux kernel did not properly validate attributes when handling certain
requests. A local attacker with the CAP_NET_ADMIN could use this to cause a
denial of service (system crash). (CVE-2017-12153)
Vitaly Mayatskikh discovered that the SCSI subsystem in the Linux kernel
did not properly track reference counts when merging buffers. A local
attacker could use this to cause a denial of service (memory exhaustion).
(CVE-2017-12190)
It was discovered that the key management subsystem in the Linux kernel did
not properly restrict key reads on negatively instantiated keys. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2017-12192)
It was discovered that an integer overflow existed in the sysfs interface
for the QLogic 24xx+ series SCSI driver in the Linux kernel. A local
privileged attacker could use this to cause a denial of service (system
crash). (CVE-2017-14051)
Otto Ebeling discovered that the memory manager in the Linux kernel did not
properly check the effective UID in some situations. A local attacker could
use this to expose sensitive information. (CVE-2017-14140)
It was discovered that the ATI Radeon framebuffer driver in the Linux
kernel did not properly initialize a data structure returned to user space.
A local attacker could use this to expose sensitive information (kernel
memory). (CVE-2017-14156)
ChunYu Wang discovered that the iSCSI transport implementation in the Linux
kernel did not properly validate data structures. A local attacker could
use this to cause a denial of service (system crash). (CVE-2017-14489)
James Patrick-Evans discovered a race condition in the LEGO USB Infrared
Tower driver in the Linux kernel. A physically proximate attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. A local attacker could
use this to cause a denial of service (system crash) or possibly execute
arbitrary code, (CVE-2017-15115)
It was discovered that the key management subsystem in the Linux kernel did
not properly handle NULL payloads with non-zero length values. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2017-15274)
It was discovered that the Bluebooth Network Encapsulation Protocol (BNEP)
implementation in the Linux kernel did not validate the type of socket
passed in the BNEPCONNADD ioctl(). A local attacker with the CAP_NET_ADMIN
privilege could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. A physically proximate attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2017-16525)
It was discovered that the netfilter passive OS fingerprinting (xt_osf)
module did not properly perform access control checks. A local attacker
could improperly modify the systemwide OS fingerprint list.
(CVE-2017-17450)
It was discovered that the HMAC implementation did not validate the state
of the underlying cryptographic hash algorithm. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. A remote attacker could use
this to cause a denial of service (system crash). (CVE-2017-18017)
Gareth Evans discovered that the shm IPC subsystem in the Linux kernel did
not properly restrict mapping page zero. A local privileged attacker could
use this to execute arbitrary code. (CVE-2017-5669)
It was discovered that an integer overflow vulnerability existing in the
IPv6 implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (infinite loop). (CVE-2017-7542)
Tommi Rantala and Brad Spengler discovered that the memory manager in the
Linux kernel did not properly enforce the CONFIG_STRICT_DEVMEM protection
mechanism. A local attacker with access to /dev/mem could use this to
expose sensitive information or possibly execute arbitrary code. A local attacker could use
this to cause a denial of service (system crash) or possibly execute
arbitrary code. (CVE-2017-8824)
Mohamed Ghannam discovered a null pointer dereference in the RDS (Reliable
Datagram Sockets) protocol implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash).
(CVE-2018-5333)
ee3/4ePS discovered that a race condition existed in loop block device
implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5344)
USN-3524-1 mitigated CVE-2017-5754 (Meltdown) for the amd64
architecture in Ubuntu 14.04 LTS. This update provides the
corresponding mitigations for the ppc64el architecture. Original
advisory details:
Jann Horn discovered that microprocessors utilizing speculative execution
and indirect branch prediction may allow unauthorized memory reads via
sidechannel attacks. This flaw is known as Meltdown. A local attacker could
use this to expose sensitive information, including kernel memory.
(CVE-2017-5754)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-3.13.0-142-generic 3.13.0-142.191
linux-image-3.13.0-142-generic-lpae 3.13.0-142.191
linux-image-3.13.0-142-lowlatency 3.13.0-142.191
linux-image-3.13.0-142-powerpc-e500 3.13.0-142.191
linux-image-3.13.0-142-powerpc-e500mc 3.13.0-142.191
linux-image-3.13.0-142-powerpc-smp 3.13.0-142.191
linux-image-3.13.0-142-powerpc64-emb 3.13.0-142.191
linux-image-3.13.0-142-powerpc64-smp 3.13.0-142.191
linux-image-generic 3.13.0.142.152
linux-image-generic-lpae 3.13.0.142.152
linux-image-lowlatency 3.13.0.142.152
linux-image-powerpc-e500 3.13.0.142.152
linux-image-powerpc-e500mc 3.13.0.142.152
linux-image-powerpc-smp 3.13.0.142.152
linux-image-powerpc64-emb 3.13.0.142.152
linux-image-powerpc64-smp 3.13.0.142.152
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3583-1
CVE-2017-0750, CVE-2017-0861, CVE-2017-1000407, CVE-2017-12153,
CVE-2017-12190, CVE-2017-12192, CVE-2017-14051, CVE-2017-14140,
CVE-2017-14156, CVE-2017-14489, CVE-2017-15102, CVE-2017-15115,
CVE-2017-15274, CVE-2017-15868, CVE-2017-16525, CVE-2017-17450,
CVE-2017-17806, CVE-2017-18017, CVE-2017-5669, CVE-2017-5754,
CVE-2017-7542, CVE-2017-7889, CVE-2017-8824, CVE-2018-5333,
CVE-2018-5344
Package Information:
https://launchpad.net/ubuntu/+source/linux/3.13.0-142.191
| VAR-201801-0385 | CVE-2017-1557 | IBM WebSphere MQ Access control vulnerability |
CVSS V2: 4.0 CVSS V3: 4.3 Severity: MEDIUM |
IBM WebSphere MQ 8.0 and 9.0 could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests. IBM X-Force ID: 131547. IBM WebSphere MQ Contains an access control vulnerability. Vendors have confirmed this vulnerability IBM X-Force ID: 131547 It is released as.Service operation interruption (DoS) There is a possibility of being put into a state.
An attacker can exploit this issue to cause a denial-of-service condition
| VAR-201801-1340 | CVE-2018-3813 | FLIR Brickstream 2300 Information disclosure vulnerability in devices |
CVSS V2: 5.0 CVSS V3: 9.8 Severity: CRITICAL |
getConfigExportFile.cgi on FLIR Brickstream 2300 devices 2.0 4.1.53.166 has Incorrect Access Control, as demonstrated by reading the AVI_USER_ID and AVI_USER_PASSWORD fields via a direct request. FLIR Brickstream 2300 The device contains an information disclosure vulnerability.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. FLIR Brickstream 2300 is a customer flow analysis and statistics equipment of Canada FLIR company. An access control error vulnerability exists in the getConfigExportFile.cgi file in FLIR Brickstream 2300 version 2.0 4.1.53.166. An attacker could exploit this vulnerability to obtain information
| VAR-201712-0555 | CVE-2017-18001 | Trustwave Secure Web Gateway Vulnerabilities related to key management errors |
CVSS V2: 10.0 CVSS V3: 9.8 Severity: CRITICAL |
Trustwave Secure Web Gateway (SWG) through 11.8.0.27 allows remote attackers to append an arbitrary public key to the device's SSH Authorized Keys data, and consequently obtain remote root access, via the publicKey parameter to the /sendKey URI. Trustwave Secure Web Gateway (SWG) Contains a vulnerability related to key management errors.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. TrustwaveSecureWebGateway (SWG) is a Web security gateway product from Trustwave Corporation of the United States. Security vulnerabilities existed in TrustwaveSWG 11.8.0.27 and earlier
| VAR-201712-0537 | CVE-2017-17974 | BA SYSTEMS BAS920 Device and ISC2000 Vulnerabilities related to certificate and password management in devices |
CVSS V2: 5.0 CVSS V3: 9.8 Severity: CRITICAL |
BA SYSTEMS BAS Web on BAS920 devices (with Firmware 01.01.00*, HTTPserv 00002, and Script 02.*) and ISC2000 devices allows remote attackers to obtain sensitive information via a request for isc/get_sid_js.aspx or isc/get_sid.aspx, as demonstrated by obtaining administrative access by subsequently using the credential information for the Supervisor/Administrator account. BA SYSTEMS BAS920 Device and ISC2000 The device contains vulnerabilities related to certificate and password management.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. The BAS920 and ISC2000 devices are programmable intelligent controller products from BA SYSTEMS, Denmark. BA SYSTEMS BAS Web is a building automation system running in it. A remote attacker can exploit this vulnerability to obtain sensitive information by sending a request to the isc/get_sid_js.aspx or isc/get_sid.aspx file
| VAR-201712-0583 | CVE-2017-17910 | Hoermann BiSecur Device cryptographic vulnerability |
CVSS V2: 3.3 CVSS V3: 6.5 Severity: MEDIUM |
On Hoermann BiSecur devices before 2018, a vulnerability can be exploited by recording a single radio transmission. An attacker can intercept an arbitrary radio frame exchanged between a BiSecur transmitter and a receiver to obtain the encrypted packet and the 32-bit serial number. The interception of the one-time pairing process is specifically not required. Due to use of AES-128 with an initial static random value and static data vector (all of this static information is the same across different customers' installations), the attacker can easily derive the utilized encryption key and decrypt the intercepted packet. The key can be verified by decrypting the intercepted packet and checking for known plaintext. Subsequently, an attacker can create arbitrary radio frames with the correct encryption key to control BiSecur garage and entrance gate operators and possibly other BiSecur systems as well ("wireless cloning"). To conduct the attack, a low cost Software Defined Radio (SDR) is sufficient. This affects Hoermann Hand Transmitter HS5-868-BS, HSE1-868-BS, and HSE2-868-BS devices. Hoermann BiSecur The device contains a cryptographic vulnerability.Denial of service (DoS) May be in a state. HoermannBiSecurdevices is a security door remote control device from Hoermann, Germany. A security vulnerability exists in previous versions of HoermannBiSecur device 2018
| VAR-201803-1048 | CVE-2017-17215 |
Huawei HG532 Input validation vulnerability
Related entries in the VARIoT exploits database: VAR-E-201712-0098 |
CVSS V2: 6.5 CVSS V3: 8.8 Severity: HIGH |
Huawei HG532 with some customized versions has a remote code execution vulnerability. An authenticated attacker could send malicious packets to port 37215 to launch attacks. Successful exploit could lead to the remote execution of arbitrary code. Huawei HG532 Contains an input validation vulnerability.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. The HuaweiHG532 series router is a wireless router product for home and small office users. Huawei HG532 is prone to a remote code-execution vulnerability. Failed exploit attempts will likely cause a denial-of-service condition
| VAR-201712-0564 | CVE-2017-17888 | Anti-Web In OS Command injection vulnerability |
CVSS V2: 9.0 CVSS V3: 8.8 Severity: HIGH |
cgi-bin/write.cgi in Anti-Web through 3.8.7, as used on NetBiter / HMS, Ouman EH-net, Alliance System WS100 --> AWU 500, Sauter ERW100F001, Carlo Gavazzi SIU-DLG, AEDILIS SMART-1, SYXTHSENSE WebBiter, ABB SREA, and ASCON DY WebServer devices, allows remote authenticated users to execute arbitrary OS commands via crafted multipart/form-data content, a different vulnerability than CVE-2017-9097. Anti-Web Is OS A command injection vulnerability exists. This vulnerability CVE-2017-9097 Is a different vulnerability.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. NetBiter/HMS, etc. are gateway devices produced by different companies. Anti-Web is an anti-virus component used in it. Security vulnerabilities exist in Anti-Web 3.8.7 and previous versions of cgi-bin/write.cgi files in various products
| VAR-201803-0204 | CVE-2017-17326 | Huawei Mate 9 Pro Smartphone software access control vulnerability |
CVSS V2: 2.1 CVSS V3: 4.6 Severity: MEDIUM |
Huawei Mate 9 Pro Smartphones with software of LON-AL00BC00B139D; LON-AL00BC00B229 have an activation lock bypass vulnerability. The smartphone is supposed to be activated by the former account after reset if find my phone function is on. The software does not have a sufficient protection of activation lock. Successful exploit could allow an attacker to bypass the activation lock and activate the smartphone by a new account after a series of operation. HuaweiMate9Pro is a smartphone from China's Huawei company. Multiple Huawei Smartphones are prone to a local security-bypass vulnerability.
Attackers can exploit this issue to bypass certain security restrictions to perform unauthorized actions. This may aid in further attacks
| VAR-201803-1031 | CVE-2017-17199 | plural Huawei Product out-of-bounds vulnerability |
CVSS V2: 4.3 CVSS V3: 5.9 Severity: MEDIUM |
Huawei DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00 have an out-of-bounds read vulnerability due to the improper processing of malformed H323 messages. A remote attacker that controls a server could exploit this vulnerability by sending malformed H323 reply messages to a target device. Successful exploit could make the device read out of bounds and probably make a service unavailable. plural Huawei The product contains an out-of-bounds vulnerability.Service operation interruption (DoS) There is a possibility of being put into a state. Huawei DP300 and other products are all products of China Huawei. The DP300 is a video conferencing terminal. The RP200 is a video conferencing machine. The following products and versions are affected: Huawei DP300 V500R002C00 Version, RP200 V500R002C00 Version, V600R006C00 Version; TE30 V100R001C10 Version, V500R002C00 Version, V600R006C00 Version; TE40 V500R002C00 Version, V600R006C00 Version; TE50 V500R002C00 Version, V600R006C00 Version; TE60 V100R001C10 Version, V500R002C00 Version, Version V600R006C00