This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
Fix for multiple security vulnerabilities in BitStream. #139
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 multiple security relevant fixes for RakNet. One of these was brought to our attention by @Mellnik.
CVSS Base score: 7.6
CVSS Temporal score: 7.1
CVSS Overall score: 7.1
CVSS v3 Vector: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H/E:F/RL:O/RC:C
The security implications of these issues are multifold and spread throughout RakNet. These range from risks of leaking arbitrary data (which can also include data outside the running application), writing data to memory (and potentially also files), and also potential DoS-attacks.
As far as our investigation goes, these vulnerabilities can not be used to bypass server authentication. This means that servers which require authentication (f.e. through a password) are not vulnerable by these issues through anonymous access.
If the server doesn't require prior authentication or if an attacker successfully authenticates with the server, it is however vulnerable by multiple attack vectors. Usage of certain (optional) RakNet features can increase the risk significantly, though it must be noted that even if only the standard functionality is used, there's a very high risk of at least suffering potential data leaks as well as being vulnerable to DoS-attacks.