| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially redirect accesses to MMIO memory resulting in loss of guest memory integrity. |
| A vulnerability in the LZX data algorithm for Microsoft Compiled HTML Help (CHM) file scanning in ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device.
This vulnerability is due to improper boundary checks when applying the LZX data algorithm to CHM files during the decoder stage, which may result in buffer overflow. An attacker could exploit this vulnerability by sending a crafted CHM file for scanning. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. |
| Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX
may overflow the calculation of the encoded output size and write past the end
of the caller-supplied output buffer.
Impact summary: No path by which an attacker can trigger this has been
identified. An application that passes an input length near INT_MAX to
EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting
its own memory, but it must itself supply such a length.
CWE: CWE-190: Integer Overflow or Wraparound
Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied
length into an output buffer that the caller allocates. The caller is expected
to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the
arithmetic that computes the encoded length overflows a signed integer, so the
function writes more data than the documented output size. The result is a
heap buffer overflow in the calling process.
Reaching this requires an application to pass an input length near INT_MAX to
EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode
buffers of that size, and the command line tools cannot practically be made to
do so: the limits on reading a proxy password from a file and on bignum sizes
prevent it. An application that accepts an attacker-controlled length and
forwards it to EVP_EncodeBlock() without its own bound check is exposed.
The severity is Low because no attacker-controlled path to the overflow is
known. The caller must already hold a buffer of about two gigabytes before the
defect can be reached.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| A heap-based buffer overflow was found in Corosync's Totem SRP membership commit token handling. The sanity check for memb_commit_token messages validates only minimum length and address-entry counts, not an upper bound against the fixed commit_token_storage buffer. A network-adjacent attacker who can deliver a crafted oversized commit token to a node in the GATHER membership state may overflow the heap-allocated totemsrp instance, leading to memory corruption and denial of service. |
| Heap-based buffer overflow in Microsoft Windows Media Foundation allows an authorized attacker to elevate privileges locally. |
| Heap-based buffer overflow in Windows USB Driver allows an unauthorized attacker to elevate privileges with a physical attack. |
| Heap-based buffer overflow in Windows Client for NFS allows an authorized attacker to elevate privileges locally. |
| Heap-based buffer overflow in Windows SMB allows an authorized attacker to execute code over a network. |
| Heap-based buffer overflow in HID Parser Library allows an unauthorized attacker to elevate privileges with a physical attack. |
| Insufficient granularity of access control in Windows IKE Extension allows an authorized attacker to perform spoofing locally. |
| Heap-based buffer overflow in Windows Universal Disk Format File System Driver (UDFS) allows an authorized attacker to elevate privileges locally. |
| Heap-based buffer overflow in Windows Sensor Data Service allows an authorized attacker to elevate privileges locally. |
| Heap-based buffer overflow in Windows DHCP Client allows an authorized attacker to elevate privileges over an adjacent network. |
| Time-of-check time-of-use (toctou) race condition in Windows DHCP Server allows an authorized attacker to execute code over a network. |
| Heap-based buffer overflow in Windows Media Player allows an unauthorized attacker to execute code over a network. |
| Heap-based buffer overflow in Windows Local Security Authority Subsystem Service (LSASS) allows an authorized attacker to elevate privileges locally. |
| Heap-based buffer overflow in Windows Local Security Authority Subsystem Service (LSASS) allows an authorized attacker to elevate privileges locally. |
| Open Robotics RViz fillIndexBuffer Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Open Robotics RViz. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the handling of mesh resources in PointCloud and Marker displays. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-32652. |
| Krita TIF File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Krita. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of TIF files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28517. |