CVE-2018-1285 - apache log4net vulnerability
Asked by Phillip Jubb:

Recently our fortinet security device has been reporting a vulnerability on my dev machine, stating the Apche log4net is vulverable.

It turns out it is tigger on log4net.dll inside my sourctree program folder on windows 10.

My IT manager is keen for me to remove sourcetree but as I use it regularly, I don;t want to lose this tool.

Is anyone else have troubles with this CVE? Where might I go to report a issue?


Answers:
author: Vipin Yadav
body: It has been taken care and will be released soon in next release of Sourcetree 3.4.8 in which log4net is updated to v.2.0.14

Thanks,

comments: author: Craig.Waddington
body: Hi [@Vipin Yadav](/t5/user/viewprofilepage/user-id/4426727)

We are using 3.4.8 and it is still reporting as Vulnerable for both OpenSSL and Log4net.dll, we have over 300 devices using Sourcetree.

Can you please advise.

OpenSSL is 1.1.1.10

![Version.png](https://community.atlassian.com/t5/image/serverpage/image-id/190356i7BA13C1A25012BFF/image-size/large?v=v2&px=999 "Version.png")

![OpenSSL.version1.png](https://community.atlassian.com/t5/image/serverpage/image-id/190359i0C87964CF9EB2F69/image-size/large?v=v2&px=999 "OpenSSL.version1.png")

![Vulnerable.png](https://community.atlassian.com/t5/image/serverpage/image-id/190358i9107612283825E21/image-size/large?v=v2&px=999 "Vulnerable.png")


author: Vipin Yadav
body: It looks like that dll is found in old version. So you need to remove app-3.4.7 from **C:\\Users\\XXX\\AppData\\Local\\SourceTree** . When there is any version of Sourcetree is available then it gets downloaded into **C:\\Users\\XXX\\AppData\\Local\\SourceTree** with new folder and we updates from there. Currently old version cleanup from **AppData** is not supported.


author: Matt Perkins
body: What about the openssl.exe? That is not in the app-3.4.7 directory. What do we do about this?


author: Albert
body: Yes we have the same issue and we are waiting for an Update. If i'm not wrong they have to update log4net.dll to v.2.0.12


author: Rene
body: Same here. December now, using 3.4.7, issue still present...

comments: author: Kushal
body: Hi Rene,

Apparently, no features which allow the Apache log4net vulnerability to be exploited have been implemented. Theoretically, even if Fortinet reports the CVE, it would be safe to say that it cannot be used to cause a breach.

From my understanding, we will need to wait for a major update, probably 4.x.x for the Apache log4net version to be changed.

Let's add a vote each and watch the issue to motivate the change.


author: Kushal
body: #### CVE-2018-1285 Description {#toc-hId--535218088}

Apache log4net versions before 2.0.10 do not disable XML external entities when parsing log4net configuration files. This allows for XXE-based attacks in applications that accept attacker-controlled log4net configuration files.

#### Observation {#toc-hId-1952294745}

Forticlient reports the vulnerability as seen below:

![CVE-2018-1285 - apache log4net vulnerability.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/158631iC8F89E7382905F3B/image-size/large?v=v2&px=999 "CVE-2018-1285 - apache log4net vulnerability.PNG")

The issue has been reported here:

[Source Tree for windows - v3.4.5: security Vulnerability CVE-2018-1285 for log4net](https://jira.atlassian.com/browse/SRCTREEWIN-13678?jql=text%20~%20%22CVE-2018-1285%22)

Add vote and watch to get it resolved in future updates.

#### Solution {#toc-hId-144840282}

Apache log4net should be updated to version 2.0.10 or later version in the next updates.


Tags: cve