due to infinite loop in rtmpdump functions. Infinite loop can be triggered by capture file with wrong sequence or invalid packets in capture file. Infinite loop can be triggered by request/response with wrong sequence numbers or invalid packet. Infinite loop can be also triggered by request/response with invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by request/response with invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by request/response with invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet. Infinite loop can be also triggered by invalid packet

Vulnerability summary:

- CVE-2022-0586: "Infinite loop can be triggered by request/response with invalid packet."
- CVE-2022-0585: "Infinite loop can be triggered by request/response with infinite sequence numbers."

New Method :

The new method to fix the infinite loop problem is to use packet. This can be done by submitting a request with the following code:

47 41
48 72
49 43
50 44 \x0b\x7d

Timeline

Published on: 02/14/2022 22:15:00 UTC
Last modified on: 04/01/2022 17:32:00 UTC

References