This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
Fix memory leak in TCPInterface (CVSS score: 4.8) #125
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Luke1410
changed the title
Luke1410
changed the title
Luke1410
changed the title
Luke1410
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of a security relevant fix for RakNet which was brought to our attention by a user. The issue has already been fixed in SLikeNet 0.1.1 (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: 5.3
CVSS Temporal score: 4.8
CVSS Overall score: 4.8
CVSS v3 Vector: AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C
The security implications of the issue are medium to low in our opinion. Ultimately, the vulnerability can be utilized to run a DoS attack on a susceptible server. A successful attack will result in the server running out of memory and will eventually cause the server application to crash.
An application is however only susceptive, if it utilizes TCP connections. Furthermore, the attack is dependent on conditions which are usually outside the realm of the attacker (i.e. depends on when the server closes a TCP connection and whether internal data was already processed).
For further details, please refer to the original issue report: SLikeSoft#18