| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Assimp through 6.0.6 contains a heap out-of-bounds read vulnerability in glTFCommon::Util::ParseDataURI caused by storing the data offset in a signed char. Attackers can supply a crafted glTF file with a raw data URI whose segment starts beyond byte 127 to crash applications or leak adjacent heap memory. |
| Out of bounds read in Tint in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability in the TIFF decoder that allows attackers to corrupt heap memory by supplying a crafted TIFF image. Attackers can provide a malicious TIFF file that, when encoded in a specific output format, triggers a heap buffer over-write causing memory corruption. |
| BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the RAMFS-backed FILE implementation accepts AtomicWriteFile(record-access) requests that replace existing records with caller-controlled content. If a client replaces a record with shorter data, the backend can shrink the heap allocation and then continue processing with a trailing-copy length derived from the old layout. During that replace path, the RAMFS backend computes the trailing-copy length from the old file layout, then shrinks the heap allocation, and finally uses the stale length in memmove(). As a result, the source range of that memmove() can extend beyond the end of the reallocated heap buffer, producing a heap out-of-bounds read. This issue has been patched in versions 1.5.1 and 1.6.0. |
| BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, a BACnet/SC peer can trigger a heap out-of-bounds read (up to 3 bytes), pre-authentication, in the BACnet/SC header-option decoder. bvlc_sc_decode_proprietary_option() reads the vendor-id and option-type at fixed offsets [3],[4],[5] before checking the option's declared header length, and the option-list validator never enforces a minimum length for proprietary options. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0. |
| Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_vnc() in src/dissectors/ec_vnc.c that checks total packet length instead of remaining bytes. A malicious VNC server can send the authentication type and challenge in one short packet to leak up to 3 bytes of adjacent heap memory via the logged challenge. |
| Integer overflow or wraparound in Windows DNS allows an unauthorized attacker to disclose information over a network. |
| Out-of-bounds read in Windows GDI allows an authorized attacker to elevate privileges locally. |
| Out-of-bounds read in Windows Telephony Service allows an authorized attacker to disclose information locally. |
| Out-of-bounds read in Windows File Server Resource Management Service allows an unauthorized attacker to elevate privileges over a network. |
| Out-of-bounds read in Windows WinHTTP allows an authorized attacker to disclose information locally. |
| Out-of-bounds read in Windows GDI allows an unauthorized attacker to disclose information over a network. |
| Out-of-bounds read in Windows DNS allows an unauthorized attacker to disclose information over a network. |
| Issue summary: A server configured with the Suite B certificate flag through
SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a
fixed group list when it processes a ClientHello whose supported_groups and
key_share contain no Suite B group.
Impact summary: A remote client can send a ClientHello that makes the server
read past the end of a static array. The values read are never returned to the
client, so no memory is disclosed; on builds with sanitizers or hardened
allocators the read may crash the process, causing Denial of Service.
CWE: CWE-125: Out-of-bounds Read
Description: When the Suite B certificate flag is set, OpenSSL restricts the
accepted groups to P-256 and P-384 by substituting a fixed two-element list
for the configured group list. The tuple machinery used for key-share
selection was not updated for this substitution: tls1_get_group_tuples() still
returns the configured tuples, which by default describe eight groups. The
server-side walk in tls_parse_ctos_key_share() then advances through the
two-element list using those tuple counts without checking the cumulative
offset against the number of groups present.
Only applications that call SSL_CTX_set_cert_flags() with
SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The
openssl s_server -suiteB_128 option sets an X.509 verification parameter
instead, so the stock command line server is not vulnerable. Default
configurations do not reach this code.
A client that offers only groups outside the Suite B set, such as X25519,
forces every tuple to be walked and the read to run past the array. The bytes
read are compared against client group IDs and never sent back, so no memory
is disclosed. On builds with address sanitizers or hardened allocators the
read can abort the process; in ordinary release builds it reads a few bytes of
adjacent constant data.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_socks() in src/dissectors/ec_socks.c that allows network-adjacent attackers to read heap memory via unchecked SOCKS5 username/password lengths. Attackers can send a crafted SOCKS5 authentication packet observed by Ettercap to read up to 255 bytes past the heap buffer, disclosing memory printed and logged as captured credentials. |
| GPAC before 26.07.0 contains a heap-based out-of-bounds read vulnerability in xmt_parse_mf_field() in loader_xmt.c caused by unchecked cursor advancement when splitting multi-value XMT-A fields. Attackers can supply a crafted XMT scene file opened with MP4Box to make xmt_parse_string() read past the heap buffer and crash the process. |
| A maliciously crafted DWG or DXF file containing a crafted field format string, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to read sensitive data from process memory. |
| BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, lighting_command_decode in src/bacnet/lighting.c decodes its first field with the bounded apdu_size - apdu_len, but every nested decode in the operation switch is called with the original full apdu_size while the read pointer has been advanced to &apdu[apdu_len]. The leaf decoders bound their reads against the size they are told, so they read up to apdu_len bytes past the end of the caller's buffer, resulting in an out-of-bounds read. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0. |
| In the Linux kernel, the following vulnerability has been resolved:
crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents
pefile_digest_pe_contents() computes the trailing-data hash length as
pelen - (hashed_bytes + certs_size). A crafted PE can make the addition
exceed pelen, causing the unsigned subtraction to underflow to ~4 GiB.
This is passed to crypto_shash_update() which reads out of bounds and
panics on unmapped vmalloc guard pages.
BUG: unable to handle page fault for address: ffffc900038d8000
Oops: Oops: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:sha256_blocks_generic (lib/crypto/sha256.c:152)
Call Trace:
<TASK>
__sha256_update (lib/crypto/sha256.c:208)
crypto_sha256_update (crypto/sha256.c:142)
verify_pefile_signature (crypto/asymmetric_keys/verify_pefile.c:436)
kexec_kernel_verify_pe_sig (kernel/kexec_file.c:151)
__do_sys_kexec_file_load (kernel/kexec_file.c:406)
do_syscall_64 (arch/x86/entry/syscall_64.c:94)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
</TASK>
Kernel panic - not syncing: Fatal exception
Validate that the addition does not overflow and the result does not
exceed pelen before the subtraction. Return -ELIBBAD on failure. |
| A maliciously crafted DXF file containing crafted VBA project data, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to read sensitive data from process memory. |