diff --git a/mRemoteNGDocumentation/known_issues.rst b/mRemoteNGDocumentation/known_issues.rst index 2a9f71a8..0c087d01 100644 --- a/mRemoteNGDocumentation/known_issues.rst +++ b/mRemoteNGDocumentation/known_issues.rst @@ -29,6 +29,29 @@ Per the MS documentation, the only way around this is to do the following: - Uninstall `KB4103727 `_ +Log4net vulnerability CVE-2018-1285 +=================================== + +Log4Net is an external library on which mRepoteNG application relies on. While the nightly builds are using the latest version of log4net that do not have the `CVE-2018-1285 `_ vulnerability, older releases require manual patching. + +1. Download latest version of log4net from `apache.org `_ - currently is v2.0.15 + +2. Copy log4net.dll from net40 folder into mRemoteNG install folder (default *C:\\Program Files (x86)\\mRemoteNG\\* ) + +3. Edit *mRemoteNG.exe.config* and add the following section under the assembly binding for ``WeifenLuo.WinFormsUI.Docking`` + +:: + + + + + + + + +.. highlights:: + Make sure the newer log4net version in the ``bindingRedirect`` section of *mRemoteNG.exe.config* file matches the version of the log4net.dll copied over at step #2. Please refer to `Microsoft documentation `_ for more details related to assembly binding in .NET applications. + I can't open more than X number of RDP sessions. New sessions fail with error code 3334 ======================================================================================= The issue here is likely the amount of resources available to the RDP component to open the connection. This was alleviated in `MR-714 `_ and `MR-864 `_