CVE-2022-27938: Reachable Assertion

stbimage.h aka the stb image loader 2.19, as used in libsixel and other products, has a reachable assertion in stbicreatepngimageraw...

CVE-2022-24777 Denial of Service via reachable assertion in grpc-swift

grpc-swift is the Swift language implementation of gRPC, a remote procedure call RPC framework. Prior to version 1.7.2, a grpc-swift server is vulnerable to a denial of service attack via a reachable assertion. This is due to incorrect logic when handling GOAWAY frames. The attack is low-effort: ...

CVE-2022-24777 Denial of Service via reachable assertion in grpc-swift

grpc-swift is the Swift language implementation of gRPC, a remote procedure call RPC framework. Prior to version 1.7.2, a grpc-swift server is vulnerable to a denial of service attack via a reachable assertion. This is due to incorrect logic when handling GOAWAY frames. The attack is low-effort: ...

CVE-2022-24777

grpc-swift is the Swift language implementation of gRPC, a remote procedure call RPC framework. Prior to version 1.7.2, a grpc-swift server is vulnerable to a denial of service attack via a reachable assertion. This is due to incorrect logic when handling GOAWAY frames. The attack is low-effort: ...

DEBIAN-CVE-2022-0635

Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check...

Authentication flaw

Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check...

CVE-2022-0635

Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check...

CVE-2022-0635: Reachable Assertion

Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

DEBIAN-CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-25484

CVE-2022-25484 affects tcpreplay’s 4.4.1 release, specifically the tcpprep component. The primary vulnerability details in the initial CVE describe a reachable assertion (assert(l2len > 0)) in packet2tree() within tree.c (tcpprep 4.4.1). Connected sources corroborate multiple memory/heap-relat...

CVE-2022-25484: Reachable Assertion

tcpprep v4.4.1 has a reachable assertion assertl2len 0 in packet2tree at tree.c in tcpprep v4.4.1...

CVE-2022-0667: Reachable Assertion

When the vulnerability is triggered the BIND process will exit. BIND 9.18.0...

PT-2022-17319 · Tcpprep +2 · Tcpprep +2

Name of the Vulnerable Software and Affected Versions: tcpprep version 4.4.1 Description: The issue is related to a reachable assertion in the packet2tree function at tree.c in tcpprep. This assertion is assertl2len 0, indicating a potential problem when the l2len variable is not greater than 0...

ISC BIND 9.18.0 < 9.18.1 Assertion Failure (CVE-2022-0667)

The version of ISC BIND installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2022-0667 advisory. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number...