221 matches found
Information disclosure
In CPUID CPU-Z through 1.81, there are improper access rights to a kernel-mode driver e.g., cpuz143x64.sys for version 1.43 that can result in information disclosure or elevation of privileges, because of an arbitrary read of any physical address via ioctl 0x9C402604. Any application running on t...
CVE-2017-15302
In CPUID CPU-Z through 1.81, there are improper access rights to a kernel-mode driver e.g., cpuz143x64.sys for version 1.43 that can result in information disclosure or elevation of privileges, because of an arbitrary read of any physical address via ioctl 0x9C402604. Any application running on t...
CVE-2017-15302
CVE-2017-15302 affects CPUID CPU-Z (Windows) up to version 1.81. The root cause is improper access rights to the kernel-mode driver (cpuz143_x64.sys) that allows an arbitrary read of any physical address via ioctl 0x9C402604 and the driver to map any physical page, returning the map page address ...
CVE-2017-15303
In CPUID CPU-Z before 1.43, there is an arbitrary memory write that results directly in elevation of privileges, because any program running on the local machine while CPU-Z is running can issue an ioctl 0x9C402430 call to the kernel-mode driver e.g., cpuz141x64.sys for version 1.41...
CVE-2017-15303
CVE-2017-15303 affects CPUID CPU-Z prior to 1.43. The flaw allows an arbitrary memory write via an ioctl 0x9C402430 to the kernel-mode driver (cpuz141_x64.sys for v1.41), enabling local elevation of privileges on the same host. This is a kernel-space write condition originating from userland inte...
CVE-2017-15302
In CPUID CPU-Z through 1.81, there are improper access rights to a kernel-mode driver e.g., cpuz143x64.sys for version 1.43 that can result in information disclosure or elevation of privileges, because of an arbitrary read of any physical address via ioctl 0x9C402604. Any application running on t...
qemu-kvm security, bug fix, and enhancement update
1.5.3-126.el7 - kvm-virtio-recalculate-vq-inuse-after-migration.patch bz1376542 - Resolves: bz1376542 RHSA-2016-1756 breaks migration of instances 1.5.3-125.el7 - kvm-nbd-server-Set-ONONBLOCK-on-client-fd.patch bz1285453 - Resolves: bz1285453 An NBD client can cause QEMU main loop to block when...
SuSE 11.3 Security Update : glibc (SAT Patch Number 10259)
glibc has been updated to fix security issues and bugs : - Fix crashes on invalid input in IBM gconv modules. CVE-2014-6040 / CVE-2012-6656, bsc894553, bsc894556, GLIBC BZ 17325, GLIBC BZ 14134 - Avoid infinite loop in nssdns getnetbyname. CVE-2014-9402 - Don't touch user-controlled stdio locks i...
SuSE 11.3 Security Update : kvm (SAT Patch Number 9739)
kvm has been updated to fix issues in the embedded qemu : - An integer overflow flaw was found in the QEMU block driver for QCOW version 1 disk images. A user able to alter the QEMU disk image files loaded by a guest could have used this flaw to corrupt QEMU process memory on the host, which coul...
Design/Logic Flaw
Xen, when using x86 Intel processors and the VMX virtualization extension is enabled, does not properly handle cpuid instruction emulation when exiting the VM, which allows local guest users to cause a denial of service guest crash via unspecified vectors...
CVE-2011-1936
Xen, when using x86 Intel processors and the VMX virtualization extension is enabled, does not properly handle cpuid instruction emulation when exiting the VM, which allows local guest users to cause a denial of service guest crash via unspecified vectors...
CVE-2011-1936
CVE-2011-1936 concerns the Xen hypervisor on x86 with VMX enabled. The issue is that cpuid instruction emulation is not properly handled when exiting a virtual machine, which can allow a local guest user to trigger a denial of service (guest crash) via unspecified vectors. The description does no...
SuSE 10 Security Update : Xen (ZYPP Patch Number 7654)
A security bug was fixed in Xen - A bug was found in the way Xen handles CPUID instruction emulation during VM exits. An unprivileged guest user can potentially use this flaw to crash the guest. CVE-2011-1936 This issue only affected systems running on x86 architecture with Intel processor and VM...
kernel: xen: vmx: insecure cpuid vmexit
Xen, when using x86 Intel processors and the VMX virtualization extension is enabled, does not properly handle cpuid instruction emulation when exiting the VM, which allows local guest users to cause a denial of service guest crash via unspecified vectors...
CPUID-based Context Keyed Payload Encoder
This is a Context-Keyed Payload Encoder based on CPUID and Shikata Ga Nai. This module requires Metasploit: https://metasploit.com/download Current source: https://github.com/rapid7/metasploit-framework require 'rex/poly' class MetasploitModule 'CPUID-based Context Keyed Payload Encoder',...
kernel security and bug fix update
2.6.9-78.0.13.0.1.EL - fix entropy flag in bnx2 driver to generate entropy pool John Sobecki orabug 5931647 - fix skb alignment that was causing sendto to fail with EFAULT Olaf Kirch orabug 6845794 - fix enomem due to larger mtu size page alloc Zach Brown orabug 5486128 - fix percpu api bugon wit...
linux/x86 - execve /bin/sh xored for Intel x86 CPUID 41 bytes
linux/x86 execve /bin/sh xored for Intel x86 CPUID 41 bytes. Shellcode exploit for linx86 platform / linux/x86 execve"/bin/sh", "/bin/sh", NULL / xor'ed against Intel x86 CPUID - 41 bytes The idea behind this shellcode is to use a weak pre-shared secret between the attacker and the attacked...
linux/x86 execve /bin/sh xored for Intel x86 CPUID 41 bytes
Exploit for linux/x86 platform in category shellcode =========================================================== linux/x86 execve /bin/sh xored for Intel x86 CPUID 41 bytes =========================================================== / linux/x86 execve"/bin/sh", "/bin/sh", NULL / xor'ed against...
linux/x86 execve /bin/sh xored for Intel x86 CPUID 41 bytes
No description provided by source. / linux/x86 execve"/bin/sh", "/bin/sh", NULL / xor'ed against Intel x86 CPUID - 41 bytes The idea behind this shellcode is to use a weak pre-shared secret between the attacker and the attacked machine. So if a 3rd party side would try to run this shellcode and...