| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A buffer overread caused by an integer-overflow in Proc/SProcXResQueryClientIds in X.Org xwayland before 24.1.15 and X Server before 21.1.26 could be used by attackers on authenticated X clients to crash the server or leak out information. |
| Buffer over-read in PostgreSQL dict_int allows a database user to disclose portions of server memory, via a zero-length token. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| Improper handling of overlap between protected memory ranges in the Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker to cause misconfigurations in the RMP potentially resulting in loss of integrity. |
| Buffer over-read in PostgreSQL parallel B-tree scans allows an object creator to read attacker-chosen server-memory addresses, via a function incorrectly marked PARALLEL SAFE or STABLE to make participating workers build different scan-key arrays. Within major versions 17-18, minor versions before PostgreSQL 18.7 and 17.12 are affected. Versions before PostgreSQL 17 are unaffected. |
| Buffer over-read in Windows Kernel allows an authorized attacker to disclose information locally. |
| Buffer over-read in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally. |
| A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. |
| Incorrect default permissions and Product released in Non-Release configuration vulnerability in OpenText Identity Console on Windows, Linux, and 64 bit allows Retrieve Embedded Sensitive Data.
This issue affects Identity Console: from 1.8 through 25.2. |
| Buffer over-read in Microsoft Office Excel allows an unauthorized attacker to disclose information over a network. |
| Buffer over-read in Microsoft Office Word allows an unauthorized attacker to disclose information over a network. |
| Buffer over-read in Windows Active Directory Certificate Services allows an authorized attacker to disclose information over a network. |
| Buffer over-read in Windows Performance Counters allows an authorized attacker to disclose information locally. |
| Buffer over-read in Windows iSCSI Target Service allows an unauthorized attacker to disclose information over a network. |
| Buffer over-read in Windows COM+ Event System Service allows an authorized attacker to disclose information locally. |
| Buffer over-read in SQL Server allows an authorized attacker to disclose information over a network. |
| Buffer over-read in Microsoft Windows SCSI Class System File allows an authorized attacker to disclose information locally. |
| Buffer over-read in Microsoft Office allows an unauthorized attacker to disclose information over a network. |
| Buffer over-read in Microsoft Office allows an unauthorized attacker to disclose information over a network. |
| Buffer over-read in SQL Server allows an unauthorized attacker to disclose information over a network. |
| iopress is a native HTTP server for Node.js with platform-specific async I/O. Prior to version 1.0.5, the chunked-transfer-encoding HTTP request parser in @iopress/core reads past the end of the input buffer when a request declares a chunk size larger than the body actually received. This results in a heap-buffer-over-read. This issue has been patched in version 1.0.5. |
