1761 matches found
The vulnerability of the memcpy function in the PowerSuite 2 software package, related to a buffer overflow error, allows an attacker to corrupt data and cause unstable operation of the program.
The vulnerability of the memcpy function in the PowerSuite 2 software package is related to a buffer overflow error. Exploiting this vulnerability can allow an attacker to trigger a buffer overflow, resulting in data corruption or unstable program behavior...
UBUNTU-CVE-2018-16885
A flaw was found in the Linux kernel that allows the userspace to call memcpyfromiovecend and similar functions with a zero offset and buffer length which causes the read beyond the buffer boundaries, in certain cases causing a memory access fault and a system halt by accessing invalid memory...
Buffer overflow
A Buffer Error vulnerability exists in PowerSuite 2, all released versions VW3A8104 & Patches, which could cause an overflow in the memcpy function, leading to corruption of data and program instability...
CVE-2018-7796
A Buffer Error vulnerability exists in PowerSuite 2, all released versions VW3A8104 & Patches, which could cause an overflow in the memcpy function, leading to corruption of data and program instability...
CVE-2018-7796
CVE-2018-7796 concerns Schneider Electric PowerSuite 2 (VW3A8104 and patches). The root cause is a buffer overflow in memcpy leading to data corruption and program instability across all released versions. No exploits or remediation details are provided in the connected documents.
Information disclosure
The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system...
CVE-2018-19320
The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system...
WhatsApp - RTP Processing Heap Corruption Exploit
Exploit for Android platform in category dos / poc Heap corruption can occur when the WhatsApp mobile application receives a malformed RTP packet. 08-31 15:43:50.721 9428 9713 F libc : Fatal signal 11 SIGSEGV, code 1, fault addr 0x7104200000 in tid 9713 Thread-11 08-31 15:43:50.722 382 382 W :...
WhatsApp - RTP Processing Heap Corruption
WhatsApp - RTP Processing Heap Corruption Heap corruption can occur when the WhatsApp mobile application receives a malformed RTP packet. 08-31 15:43:50.721 9428 9713 F libc : Fatal signal 11 SIGSEGV, code 1, fault addr 0x7104200000 in tid 9713 Thread-11 08-31 15:43:50.722 382 382 W : debuggerd:...
tcpreplay heap buffer overflow vulnerability (CNVD-2018-20537)
Tcpreplay is a set of open source utilities for editing and replaying network traffic for UNIX based operating systems. A heap buffer overflow vulnerability exists in the sendpackets.c file in Tcpreplay version 4.3.0, which stems from the 'getnextpacket' function using the 'memcpy' function in an...
DEBIAN-CVE-2018-17582
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
CVE-2018-17582
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
CVE-2018-17582
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
Heap overflow
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
CVE-2018-17582
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
CVE-2018-17582
Tcpreplay v4.3.0 beta1 contains a heap-based buffer over-read. The getnextpacket function in the sendpackets.c file uses the memcpy function unsafely to copy sequences from the source buffer pktdata to the destination prevpacket-pktdata. This will result in a Denial of Service DoS and potentially...
CVE-2018-11863
In all android releases Android for MSM, Firefox OS for MSM, QRD Android from CAF using the linux kernel, lack of check of input received from firmware to calculate the length of WMA roam synch buffer can lead to buffer overwrite during memcpy...
Buffer overflow
In all android releases Android for MSM, Firefox OS for MSM, QRD Android from CAF using the linux kernel, possible buffer overflow while incrementing the logbuf of type uint64t in memcpy function, since the logbuf pointer can access the memory beyond the size to store the data after pointer...
Buffer overflow
In all android releases Android for MSM, Firefox OS for MSM, QRD Android from CAF using the linux kernel, lack of check of input received from firmware to calculate the length of WMA roam synch buffer can lead to buffer overwrite during memcpy...
CVE-2018-11265
In all android releases Android for MSM, Firefox OS for MSM, QRD Android from CAF using the linux kernel, possible buffer overflow while incrementing the logbuf of type uint64t in memcpy function, since the logbuf pointer can access the memory beyond the size to store the data after pointer...