CVE-1999-0199

manual/search.texi in the GNU C Library aka glibc before 2.2 lacks a statement about the unspecified tdelete return value upon deletion of a tree's root, which might allow attackers to access a dangling pointer in an application whose developer was unaware of a documentation update from 1999...

CVE-1999-0199: Unchecked Return Value

manual/search.texi in the GNU C Library aka glibc before 2.2 lacks a statement about the unspecified tdelete return value upon deletion of a tree's root, which might allow attackers to access a dangling pointer in an application whose developer was unaware of a documentation update from 1999...

PT-2020-7012

Name of the Vulnerable Software and Affected Versions glibc versions prior to 2.2 Description The issue is related to the manual/search.texi in the GNU C Library, where a lack of documentation about the return value of the tdelete function when deleting a tree's root might allow attackers to acce...

SUSE SLES12 Security Update : libxslt (SUSE-SU-2020:0920-2)

This update for libxslt fixes the following issue : CVE-2019-18197: Fixed a dangling pointer in xsltCopyText which may have led to information disclosure bsc1154609. Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable...

SUSE-SU-2020:0920-2 Security update for libxslt

This update for libxslt fixes the following issue: - CVE-2019-18197: Fixed a dangling pointer in xsltCopyText which may have led to information disclosure bsc1154609...

CVE-2020-8231

Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data...

UBUNTU-CVE-2020-8231

Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data...

PT-2020-6189

Name of the Vulnerable Software and Affected Versions libcurl versions 7.29.0 through 7.71.1 Description The issue is related to the use of a dangling pointer, which can cause libcurl to use the wrong connection when sending data. This can lead to a remote attacker gaining access to confidential...

CVE-2020-3671: Use After Free

Use-after-free issue could occur due to dangling pointer when generating a frame buffer in OpenGL ES in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in APQ8009, Nicobar, QCM2150, QCS405, Saipan, SDM845, SM8150, SM8250, SXR2130...

VMware ESXi Use-After-Free / Out-Of-Bounds Access Vulnerability

Several security issues have been identified in the VMware ESIx virtual machine monitor VMM. A use-after-free UAF vulnerability in PVNVRAM, a missing return value check in EHCI USB controller leading to private heap information disclosure, and several out-of-bounds reads. Overview ======= We...

Apache Guacamole < 1.2.0 Multiple Vulnerabilities

Apache Guacamole is prone to multiple vulnerabilities. Copyright C 2020 Greenbone Networks GmbH Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-or-later This program is free software; you ca...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

SUSE-SU-2020:1409-1 Security update for libxslt

This update for libxslt fixes the following issues: Security issues fixed: - CVE-2019-13118: Fixed a read of uninitialized stack data bsc1140101. - CVE-2019-13117: Fixed a uninitialized read which allowed to discern whether a byte on the stack contains certain special characters bsc1140095. -...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

kernel: double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c

A flaw was found in the allocatetracebuffer in kernel/trace/trace.c in the debug subsystem, when failure to allocate a dynamic percpu area, a resource cleanup is called. The pointer buf-buffer still holds the address and is not set to NULL, which can cause a use-after-free problem, leading to a...

RUSTSEC-2020-0009 `read_scalar` and `read_scalar_at` allow transmuting values without `unsafe` blocks

The readscalar and readscalarat functions are unsound because they allow transmuting values without unsafe blocks. The following example shows how to create a dangling reference: fn main deriveCopy, Clone, PartialEq, Debug struct S&'static str; impl flatbuffers::EndianScalar for S fn...

`read_scalar` and `read_scalar_at` allow transmuting values without `unsafe` blocks

The readscalar and readscalarat functions are unsound because they allow transmuting values without unsafe blocks. The following example shows how to create a dangling reference: fn main deriveCopy, Clone, PartialEq, Debug struct S&'static str; impl flatbuffers::EndianScalar for S fn...