OSV-2022-1261 UNKNOWN WRITE in void std::__1::allocator_traits<std::__1::allocator<wabt::interp::HandlerDesc> >

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=54245 Crash type: UNKNOWN WRITE Crash state: void std::1::allocatortraits void std::1::vectorwabt::interp::HandlerDesc, std::1::allocatorwabt::inter std::1::vectorwabt::interp::HandlerDesc, std::1::allocatorwabt::interp::Ha...

CVE-2022-43281

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

CVE-2022-43281

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

Design/Logic Flaw

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

CVE-2022-43281

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

CVE-2022-43281

The CVE-2022-43281 entry concerns wasm-interp v1.0.29, which is reported to have a heap overflow in the vector implementation: std::vector::size() as implemented in /bits/stl_vector.h. According to the primary description, this vulnerability is characterized with high impact (C, I, A) and a local...

CVE-2022-43281

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

CVE-2022-43281: Out-of-bounds Write

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector ::size at /bits/stlvector.h...

CVE-2022-43281

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector::size at /bits/stlvector.h...

OSV-2022-999 Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51972 Crash type: Heap-buffer-overflow READ Crash state: std::1::basicstring, std::1::allocatorch Exiv2::QuickTimeVideo::userDataDecoder Exiv2::QuickTimeVideo::tagDecoder...

OSV-2022-904 Heap-use-after-free in std::__1::pair<std::__1::__tree_iterator<std::__1::__value_type<geos::geom::Coor

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51406 Crash type: Heap-use-after-free READ 8 Crash state: std::1::pairstd::1::treeiteratorstd::1::valuetypegeos::geom::Coor geos::geomgraph::NodeMap::addNode geos::geomgraph::GeometryGraph::addSelfIntersectionNode...

OSV-2022-861 Heap-use-after-free in std::__1::pair<std::__1::__tree_iterator<std::__1::__value_type<geos::geom::Coor

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=51083 Crash type: Heap-use-after-free READ 8 Crash state: std::1::pairstd::1::treeiteratorstd::1::valuetypegeos::geom::Coor geos::geomgraph::NodeMap::addNode geos::operation::overlay::OverlayOp::copyPoints...

`os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

The ossocketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were changed into idiomatic rust...

GHSA-C439-CHV8-8G2J `os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

The ossocketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were changed into idiomatic rust...

OSV-2022-794 Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50629 Crash type: Heap-buffer-overflow READ 5 Crash state: std::1::basicstring, std::1::allocatorch Exiv2::QuickTimeVideo::previewTagDecoder Exiv2::QuickTimeVideo::tagDecoder...

RUSTSEC-2022-0052 `os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

The ossocketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were changed into idiomatic rust...

`os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

The ossocketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were changed into idiomatic rust...

CVE-2022-36153

tifig v0.2.2 was discovered to contain a segmentation violation via std::vector ::size const at /bits/stlvector.h...

Code injection

tifig v0.2.2 was discovered to contain a segmentation violation via std::vector ::size const at /bits/stlvector.h...

CVE-2022-36153

CVE-2022-36153 affects tifig v0.2.2, where a segmentation violation can occur through the use of std::vector::size() in /bits/stl_vector.h. The issue is documented across multiple sources (NVD entry and Red Hat/OSV/CVE lists) consistently describing a memory/segmentation fault in tifig 0.2.2. The...