CWE-416
Use After Free
Description
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Hierarchy (View 1000)
Parents
Children
none
CVEs mapped to this weakness (2,306)
page 105 of 116| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2021-21028 | 0.00 | — | 0.04 | Feb 11, 2021 | Acrobat Reader DC versions versions 2020.013.20074 (and earlier), 2020.001.30018 (and earlier) and 2017.011.30188 (and earlier) are affected by a Use After Free vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve arbitrary code execution in… | |||
| CVE-2020-36205 | — | 0.00 | — | 0.00 | Jan 22, 2021 | An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. | ||
| CVE-2018-25001 | — | 0.00 | — | 0.01 | Dec 31, 2020 | An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free. | ||
| CVE-2020-35862 | — | 0.00 | — | 0.02 | Dec 31, 2020 | An issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free. | ||
| CVE-2020-35870 | — | 0.00 | — | 0.02 | Dec 31, 2020 | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free. | ||
| CVE-2020-35873 | — | 0.00 | — | 0.02 | Dec 31, 2020 | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free. | ||
| CVE-2020-35876 | — | 0.00 | — | 0.02 | Dec 31, 2020 | An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race. | ||
| CVE-2020-35898 | — | 0.00 | — | 0.01 | Dec 31, 2020 | An issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data. | ||
| CVE-2020-35899 | — | 0.00 | — | 0.00 | Dec 31, 2020 | An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data. | ||
| CVE-2020-35900 | — | 0.00 | — | 0.00 | Dec 31, 2020 | An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free. | ||
| CVE-2020-35901 | — | 0.00 | — | 0.01 | Dec 31, 2020 | An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream. | ||
| CVE-2020-35902 | — | 0.00 | — | 0.02 | Dec 31, 2020 | An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed. | ||
| CVE-2020-35906 | — | 0.00 | — | 0.00 | Dec 31, 2020 | An issue was discovered in the futures-task crate before 0.3.6 for Rust. futures_task::waker may cause a use-after-free in a non-static type situation. | ||
| CVE-2020-35917 | — | 0.00 | — | 0.00 | Dec 31, 2020 | An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py>. | ||
| CVE-2020-27195 | — | 0.00 | — | 0.01 | Oct 22, 2020 | HashiCorp Nomad and Nomad Enterprise version 0.9.0 up to 0.12.5 client file sandbox feature can be subverted using either the template or artifact stanzas. Fixed in 0.12.6, 0.11.5, and 0.10.6 | ||
| CVE-2020-8945 | — | 0.00 | — | 0.05 | Feb 12, 2020 | The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification. | ||
| CVE-2019-16882 | — | 0.00 | — | 0.02 | Sep 25, 2019 | An issue was discovered in the string-interner crate before 0.7.1 for Rust. It allows attackers to read from memory locations associated with dangling pointers, because of a cloning flaw. | ||
| CVE-2019-16881 | — | 0.00 | — | 0.03 | Sep 25, 2019 | An issue was discovered in the portaudio-rs crate through 0.3.1 for Rust. There is a use-after-free with resultant arbitrary code execution because of a lack of unwind safety in stream_callback and stream_finished_callback. | ||
| CVE-2019-16138 | — | 0.00 | — | 0.02 | Sep 9, 2019 | An issue was discovered in the image crate before 0.21.3 for Rust, affecting the HDR image format decoder. Vec::set_len is called on an uninitialized vector, leading to a use-after-free and arbitrary code execution. | ||
| CVE-2019-16140 | — | 0.00 | — | 0.02 | Sep 9, 2019 | An issue was discovered in the chttp crate before 0.1.3 for Rust. There is a use-after-free during buffer conversion. |
- CVE-2021-21028Feb 11, 2021risk 0.00cvss —epss 0.04
Acrobat Reader DC versions versions 2020.013.20074 (and earlier), 2020.001.30018 (and earlier) and 2017.011.30188 (and earlier) are affected by a Use After Free vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve arbitrary code execution in…
- CVE-2020-36205Jan 22, 2021risk 0.00cvss —epss 0.00
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.
- CVE-2018-25001Dec 31, 2020risk 0.00cvss —epss 0.01
An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.
- CVE-2020-35862Dec 31, 2020risk 0.00cvss —epss 0.02
An issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free.
- CVE-2020-35870Dec 31, 2020risk 0.00cvss —epss 0.02
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free.
- CVE-2020-35873Dec 31, 2020risk 0.00cvss —epss 0.02
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free.
- CVE-2020-35876Dec 31, 2020risk 0.00cvss —epss 0.02
An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race.
- CVE-2020-35898Dec 31, 2020risk 0.00cvss —epss 0.01
An issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.
- CVE-2020-35899Dec 31, 2020risk 0.00cvss —epss 0.00
An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.
- CVE-2020-35900Dec 31, 2020risk 0.00cvss —epss 0.00
An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free.
- CVE-2020-35901Dec 31, 2020risk 0.00cvss —epss 0.01
An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream.
- CVE-2020-35902Dec 31, 2020risk 0.00cvss —epss 0.02
An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed.
- CVE-2020-35906Dec 31, 2020risk 0.00cvss —epss 0.00
An issue was discovered in the futures-task crate before 0.3.6 for Rust. futures_task::waker may cause a use-after-free in a non-static type situation.
- CVE-2020-35917Dec 31, 2020risk 0.00cvss —epss 0.00
An issue was discovered in the pyo3 crate before 0.12.4 for Rust. There is a reference-counting error and use-after-free in From<Py>.
- CVE-2020-27195Oct 22, 2020risk 0.00cvss —epss 0.01
HashiCorp Nomad and Nomad Enterprise version 0.9.0 up to 0.12.5 client file sandbox feature can be subverted using either the template or artifact stanzas. Fixed in 0.12.6, 0.11.5, and 0.10.6
- CVE-2020-8945Feb 12, 2020risk 0.00cvss —epss 0.05
The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification.
- CVE-2019-16882Sep 25, 2019risk 0.00cvss —epss 0.02
An issue was discovered in the string-interner crate before 0.7.1 for Rust. It allows attackers to read from memory locations associated with dangling pointers, because of a cloning flaw.
- CVE-2019-16881Sep 25, 2019risk 0.00cvss —epss 0.03
An issue was discovered in the portaudio-rs crate through 0.3.1 for Rust. There is a use-after-free with resultant arbitrary code execution because of a lack of unwind safety in stream_callback and stream_finished_callback.
- CVE-2019-16138Sep 9, 2019risk 0.00cvss —epss 0.02
An issue was discovered in the image crate before 0.21.3 for Rust, affecting the HDR image format decoder. Vec::set_len is called on an uninitialized vector, leading to a use-after-free and arbitrary code execution.
- CVE-2019-16140Sep 9, 2019risk 0.00cvss —epss 0.02
An issue was discovered in the chttp crate before 0.1.3 for Rust. There is a use-after-free during buffer conversion.