Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log4net.dll version is affected by CVE-2018-1285 #840

Closed
caseyswitzer opened this issue Oct 20, 2021 · 9 comments
Closed

log4net.dll version is affected by CVE-2018-1285 #840

caseyswitzer opened this issue Oct 20, 2021 · 9 comments
Assignees
Milestone

Comments

@caseyswitzer
Copy link

Hello,

Recently a host-based vulnerability scan picked up superputty's log4net.dll as susceptible to CVE-2018-1285.
https://nvd.nist.gov/vuln/detail/CVE-2018-1285

Can you confirm if this is a false positive?

Some employers prohibit using software in their environment that contain critical vulnerabilities.

Thanks!

@jimradford
Copy link
Owner

I was mistaken, we are using 2.0.10 and are not affected by the CVE you listed.

Regards,

Jim

@jimradford
Copy link
Owner

Unaffected

@tomangert
Copy link

Wasn't that package updated after the latest release?

Is there a way to download a later build that includes this?

@caseyswitzer
Copy link
Author

I'm running the latest stable - 1.4.0.9. It appears that for some reason that log4net.dll is being identified as version 1.2.13.0. Maybe there is a version number or identifier in this file, or file's metadata, that includes this value. Either the vulnerability scan software is incorrectly picking up the version here or maybe a version number wasn't updated on the .dll somehow.

@jimradford
Copy link
Owner

So there are a couple issues related to this, 1) the last "packaged" release (1.4.0.9) I believe has an older version of log4net as was originally reported, as far as the version is concerned it is susceptible to the vulnerability listed (although I have not spent any time to find out if the way we specifically use the library is vulnerable or not). 2) the automatic build server no longer stores artifacts, so the "nightly" or development version is no available packaged at this time, so until a new release is packaged, it will require that the source be downloaded and compiled to run the latest development version.

As a temporary "fix" I have rebuilt the last development version so the artifacts will be around for 30 days. Hopefully by then I can push out a new packaged release. Downloadable from here: https://ci.appveyor.com/project/jimradford/superputty/build/artifacts (for about 30 days)

@jimradford jimradford reopened this Oct 21, 2021
@jimradford jimradford self-assigned this Nov 21, 2021
@jimradford jimradford added this to the v1.4.10 milestone Nov 21, 2021
@jimradford
Copy link
Owner

This has been fixed as of 1.4.10, for earlier versions you can either replace the log4net.dll with a newer version or download an artifact build.

@DeanUWTSD
Copy link

Hello

log4net.dll 2.0.8 is still affected by the vulnerability but is fixed in 2.0.10. So superputty 1.4.10 is still being picked up by vulnerability scans.

@oopoopoop
Copy link

I was mistaken, we are using 2.0.10 and are not affected by the CVE you listed.

Regards,

Jim

https://github.com/jimradford/superputty/releases/tag/1.4.10
Both the zip and msi installer downloaded from the above link are still using log4net.dll 2.0.8, which is still affected by the vulnerability CVE-2018-1285.

Should we reopen this issue?

@oopoopoop
Copy link

btw, tried to manually replace the dll downloaded from this link.

SuperPuTTy won't start afterwards.

@jimradford jimradford reopened this Mar 10, 2022
@jimradford jimradford modified the milestones: v1.4.10, 1.4.0.11 Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants