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 (1,889)
page 84 of 95| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2021-24037 | — | 0.00 | — | 0.01 | Jun 15, 2021 | A use after free in hermes, while emitting certain error messages, prior to commit d86e185e485b6330216dee8e854455c694e3a36e allows attackers to potentially execute arbitrary code via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits… | ||
| CVE-2021-3518 | — | 0.00 | — | 0.00 | May 18, 2021 | There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability. | ||
| CVE-2021-29935 | — | 0.00 | — | 0.00 | Apr 1, 2021 | An issue was discovered in the rocket crate before 0.4.7 for Rust. uri::Formatter can have a use-after-free if a user-provided function panics. | ||
| CVE-2021-28305 | — | 0.00 | — | 0.01 | Mar 12, 2021 | An issue was discovered in the diesel crate before 1.4.6 for Rust. There is a use-after-free in the SQLite backend because the semantics of sqlite3_column_name are not followed. | ||
| CVE-2021-28032 | — | 0.00 | — | 0.01 | Mar 5, 2021 | An issue was discovered in the nano_arena crate before 0.5.2 for Rust. There is an aliasing violation in split_at because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or… | ||
| CVE-2021-27377 | — | 0.00 | — | 0.01 | Feb 18, 2021 | An issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free. | ||
| CVE-2021-21028 | 0.00 | — | 0.23 | 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.00 | 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.01 | 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.01 | 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.01 | 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.01 | 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.00 | 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.00 | 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.01 | 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-2021-24037Jun 15, 2021risk 0.00cvss —epss 0.01
A use after free in hermes, while emitting certain error messages, prior to commit d86e185e485b6330216dee8e854455c694e3a36e allows attackers to potentially execute arbitrary code via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits…
- CVE-2021-3518May 18, 2021risk 0.00cvss —epss 0.00
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
- CVE-2021-29935Apr 1, 2021risk 0.00cvss —epss 0.00
An issue was discovered in the rocket crate before 0.4.7 for Rust. uri::Formatter can have a use-after-free if a user-provided function panics.
- CVE-2021-28305Mar 12, 2021risk 0.00cvss —epss 0.01
An issue was discovered in the diesel crate before 1.4.6 for Rust. There is a use-after-free in the SQLite backend because the semantics of sqlite3_column_name are not followed.
- CVE-2021-28032Mar 5, 2021risk 0.00cvss —epss 0.01
An issue was discovered in the nano_arena crate before 0.5.2 for Rust. There is an aliasing violation in split_at because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or…
- CVE-2021-27377Feb 18, 2021risk 0.00cvss —epss 0.01
An issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free.
- CVE-2021-21028Feb 11, 2021risk 0.00cvss —epss 0.23
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.00
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.01
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.01
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.01
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.01
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.00
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.00
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.01
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>.