Lucene search
+L

3631 matches found

RedhatCVE
RedhatCVE
added 2023/05/04 10:21 a.m.55 views

CVE-2023-2513

A use-after-free vulnerability was found in the Linux kernel's ext4 filesystem in the way it handled the extra inode size for extended attributes. This flaw allows a privileged local user to cause a system crash or other undefined behaviors...

6.7CVSS6.4AI score0.00242EPSS
SaveExploits0References3
RedhatCVE
RedhatCVE
added 2023/05/02 5:21 p.m.35 views

CVE-2023-2483

A race condition vulnerability was found in the Linux kernel's Qualcomm EMAC Gigabit Ethernet Controller when the user physically removes the device before cleanup in the emacremove function. This flaw can eventually result in a use-after-free issue, possibly leading to a system crash or other...

6.8AI score
SaveExploits0References2
NVD
NVD
added 2023/04/27 5:15 p.m.15 views

CVE-2023-30624

Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled...

8.8CVSS7AI score0.0045EPSS
SaveExploits0References2
OSV
OSV
added 2023/04/27 5:08 p.m.17 views

GHSA-CH89-5G45-QWC7 Undefined Behavior in Rust runtime functions

Impact Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled with LLVM 16 which causes some writes, which are critical for correctness, to be...

3.9CVSS6.6AI score0.0045EPSS
SaveExploits0References6
Cvelist
Cvelist
added 2023/04/27 4:56 p.m.29 views

CVE-2023-30624 Wasmtime has Undefined Behavior in Rust runtime functions

Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled...

3.9CVSS9AI score0.0045EPSS
SaveExploits0References2
OSV
OSV
added 2023/04/27 4:56 p.m.16 views

CVE-2023-30624 Wasmtime has Undefined Behavior in Rust runtime functions

Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled...

3.9CVSS8.5AI score
SaveExploits0References4
Debian CVE
Debian CVE
added 2023/04/27 4:56 p.m.30 views

CVE-2023-30624

Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled...

8.8CVSS8.7AI score0.0045EPSS
SaveExploits0
Vulnrichment
Vulnrichment
added 2023/04/27 4:56 p.m.13 views

CVE-2023-30624 Wasmtime has Undefined Behavior in Rust runtime functions

Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled...

3.9CVSS8.8AI score0.0045EPSS
SaveExploits0References2
CNNVD
CNNVD
added 2023/04/27 12:00 a.m.10 views

Wasmtime 安全漏洞

Wasmtime, a Bytecode Consortium project, is a standalone wasm-optimized runtime for WebAssembly and WASI only. A security vulnerability exists in wasmtime versions 6.0.1 and earlier, 7.0.0, and 8.0.0, which stems from the fact that Wasmtime's implementation of managing per-instance state e.g.,...

8.8CVSS7.6AI score0.0045EPSS
SaveExploits0References3
OSV
OSV
added 2023/04/24 4:47 p.m.20 views

GHSA-QVC4-78GW-PV8P Adverserial use of `make_bitflags!` macro can cause undefined behavior

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could...

7.2AI score
SaveExploits0References3
Github Security Blog
Github Security Blog
added 2023/04/24 4:47 p.m.22 views

Adverserial use of `make_bitflags!` macro can cause undefined behavior

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could...

6.8AI score
SaveExploits0References3Affected Software1
OSV
OSV
added 2023/04/21 12:00 p.m.7 views

RUSTSEC-2023-0092 Undefined Behavior in Rust runtime functions

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-ch89-5g45-qwc7. For more information see the GitHub-hosted security advisory...

3.9CVSS6.6AI score0.0045EPSS
SaveExploits0References3
RustSec
RustSec
added 2023/04/21 12:00 p.m.11 views

Undefined Behavior in Rust runtime functions

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-ch89-5g45-qwc7. For more information see the GitHub-hosted security advisory...

8.8CVSS7AI score0.0045EPSS
SaveExploits0Affected Software1
Positive Technologies
Positive Technologies
added 2023/04/21 12:00 a.m.6 views

PT-2023-22821 · Rust +2 · Rust +2

Name of the Vulnerable Software and Affected Versions: Wasmtime versions prior to 6.0.2 Wasmtime versions prior to 7.0.1 Wasmtime versions prior to 8.0.1 Description: Wasmtime's implementation of managing per-instance state contains LLVM-level undefined behavior, which can cause runtime-level...

8.8CVSS8.5AI score0.0045EPSS
SaveExploits0References13
OSV
OSV
added 2023/04/17 4:32 p.m.25 views

GHSA-FJX5-QPF4-XJF2 Parsing borsh messages with ZST which are not-copy/clone is unsound

Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...

6.9AI score
SaveExploits0References3
Github Security Blog
Github Security Blog
added 2023/04/17 4:32 p.m.21 views

Parsing borsh messages with ZST which are not-copy/clone is unsound

Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...

6.5AI score
SaveExploits0References3Affected Software1
OSV
OSV
added 2023/04/17 12:00 p.m.17 views

RUSTSEC-2023-0035 Adverserial use of `make_bitflags!` macro can cause undefined behavior

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could...

7.2AI score
SaveExploits0References3
RustSec
RustSec
added 2023/04/17 12:00 p.m.17 views

Adverserial use of `make_bitflags!` macro can cause undefined behavior

The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could...

6.8AI score
SaveExploits0Affected Software1
RustSec
RustSec
added 2023/04/12 12:00 p.m.28 views

Parsing borsh messages with ZST which are not-copy/clone is unsound

Affected versions of borsh cause undefined behavior when zero-sized-types ZST are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy this can be achieved through a singleton, then accessing/writing to...

6.5AI score
SaveExploits0Affected Software1
Github Security Blog
Github Security Blog
added 2023/04/07 7:23 p.m.20 views

ntru-rs has unsound FFI: Wrong API usage causes write past allocated area

The following usage causes undefined behavior. rust let kp: ntru::types::KeyPair = …; kp.getpublic.exportDefault::default When compiled with debug assertions, the code above will trigger a attempt to subtract with overflow panic before UB occurs. Other mistakes e.g. using EncParams from a differe...

6.8AI score
SaveExploits0References3Affected Software1
Rows per page
Query Builder