CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

Code injection

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

UBUNTU-CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

CVE-2017-7705 : In Wireshark versions 2.2.0–2.2.5 and 2.0.0–2.0.11, the RPC over RDMA dissector could enter an infinite loop when processing certain crafted packets or malformed captures. The issue was fixed in epan/dissectors/packet-rpcrdma.c by validating offsets to prevent reading beyond the m...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2017-7705

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

PT-2017-17901

Name of the Vulnerable Software and Affected Versions Wireshark versions 2.0.0 through 2.0.11 Wireshark versions 2.2.0 through 2.2.5 Description The RPC over RDMA dissector could enter an infinite loop, triggered by packet injection or a malformed capture file. This issue was addressed by correct...

CVE-2017-7705: Loop with Unreachable Exit Condition

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset...

CVE-2016-8636

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...

Integer overflow

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...

CVE-2016-8636

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...

CVE-2016-8636

The CVE-2016-8636 issue affects the Linux kernel’s mem_check_range path in drivers/infiniband/sw/rxe/rxe_mr.c, where an integer overflow can occur. This vulnerability in Soft RoCE (RDMA over InfiniBand) allows local users to trigger memory corruption, potentially cause a denial of service, and ma...

CVE-2016-8636

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...

CVE-2016-8636

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...

UBUNTU-CVE-2016-8636

Integer overflow in the memcheckrange function in drivers/infiniband/sw/rxe/rxemr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service memory corruption, obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read...