| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Use after free in Windows Network Connection Broker allows an authorized attacker to elevate privileges locally. |
| 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. |
| Exposure of sensitive system information to an unauthorized control sphere in Windows Overlay Filter allows an authorized attacker to disclose information locally. |
| Buffer over-read in Windows Management Instrumentation 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. |
| Release of invalid pointer or reference in Windows DHCP Server allows an authorized attacker to execute code over a network. |
| Heap-based buffer overflow in Windows Partition Management Driver allows an authorized attacker to elevate privileges with a physical attack. |
| NVIDIA OpenShell for Linux contains a vulnerability in its inference-interception request parser where a sandboxed actor could exhaust processing resources by sending a chunked request that lacks body-size and chunk-count limits, causing excessive parsing work. A successful exploit of this vulnerability might lead to denial of service. |
| NVIDIA OpenShell for Linux contains a vulnerability in its gateway connection-proxy component where an attacker who can manipulate a sandbox's status metadata could cause the control-plane server to initiate connections to arbitrary internal hosts because the connection target is derived from that metadata and used without validation against the expected address range. A successful exploit of this vulnerability might lead to information disclosure and data tampering. |
| GitLab has remediated an issue in GitLab EE affecting all versions from 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to start a Duo Workflow session with elevated privileges beyond those declared by the foundational flow due to improper enforcement of privilege boundaries in certain client environments. |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.0 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to import Git repositories into projects despite administrator restrictions on import sources due to missing authorization checks. |
| Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.
Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.
CWE: CWE-401: Missing Release of Memory after Effective Lifetime
Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.
The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.
Each retained stream costs about 300 bytes, and the peer's stream credit
window paces how quickly they accumulate. A client that keeps the connection
open and keeps opening and resetting streams grows server memory without
bound. The severity is Low because growth is slow, needs a long-lived
connection, and causes no memory corruption or disclosure.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to change the GitLab Duo Code Review consent setting of a parent group due to incorrect authorization checks. |
| GitLab has remediated an issue in GitLab EE affecting all versions from 17.7 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read GitLab Duo seat assignments and usage data from other groups due to improper authorization checks. |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with an unconfirmed email address to be automatically granted Group Owner-level membership during a group import operation, due to insufficient email verification enforcement in the member identity mapping process. |
| GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user holding an MCP-scoped OAuth token to perform unauthorized issuable state changes on issues and merge requests, including approving and merging, due to incorrect authorization checks. |