This is a backport of a security relevant fix for RakNet (fixes second part of issue #102) which was brought to our attention by a user - see https://github.com/SLikeSoft/SLikeNet/issues/32 for details. The issue has already been fixed in SLikeNet 0.1.2 (see https://www.slikenet.com/).
We provide this backport for people who prefer to stick with the RakNet project and also in order to easier share this fix with other RakNet forks.
This fix works in combination with pull request #127. Therefore, both pull requests must be applied to completely resolve the issue.
The security implications are critical in our opinion. Every RakNet instance is susceptive to the attack. No authentication is required. If the attack is successful, the instance will become unresponsive for as long as the attack goes on (and quite a while afterwards - DoS attack). If the attack stops, the server will become responsible again eventually.
If an upgrade of the server side is not reasonable to resolve the vulnerability, we offer alternative approaches to mitigate attacks relying on this issue. Please contact us at security@slikesoft.com.
This is a backport of a security relevant fix for RakNet (fixes second part of issue #102) which was brought to our attention by a user - see https://github.com/SLikeSoft/SLikeNet/issues/32 for details. The issue has already been fixed in SLikeNet 0.1.2 (see https://www.slikenet.com/). We provide this backport for people who prefer to stick with the RakNet project and also in order to easier share this fix with other RakNet forks.
CVSS Base score: 7.5 CVSS Temporal score: 7.2 CVSS Overall score: 7.2 CVSS v3 vector: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:H/RL:O/RC:C
This fix works in combination with pull request #127. Therefore, both pull requests must be applied to completely resolve the issue.
The security implications are critical in our opinion. Every RakNet instance is susceptive to the attack. No authentication is required. If the attack is successful, the instance will become unresponsive for as long as the attack goes on (and quite a while afterwards - DoS attack). If the attack stops, the server will become responsible again eventually. If an upgrade of the server side is not reasonable to resolve the vulnerability, we offer alternative approaches to mitigate attacks relying on this issue. Please contact us at security@slikesoft.com.