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

Security issues #771

Closed
DanMcNamee42 opened this issue Feb 6, 2024 · 9 comments
Closed

Security issues #771

DanMcNamee42 opened this issue Feb 6, 2024 · 9 comments

Comments

@DanMcNamee42
Copy link

I was investigating using this package for use on a work project, and part of our due diligence before using packages is to run the package through a scan for vulnerabilities. Our scan found multiple security vulnerabilities with the old versions of .NetCore and Newtonsoft.Json that should be fixed by updating the packages to the current versions.

I like the package, it does exactly what we need, but with the vulnerabilities, I won't be able to get it approved. Any chance of getting the packages you are using updated to address the vulnerabilities?

Thanks!

@Numpsy
Copy link
Contributor

Numpsy commented Feb 6, 2024

When you say 'the package', do you mean the PdfPig nuget package or something else in the repo? (the main lib seems to only depend on System.ValueTuple, and then only on .NET 4.x, though adding a .NET 4.7.1 target might remove that for 4.7.1+ consumers)

@Numpsy
Copy link
Contributor

Numpsy commented Feb 6, 2024

There are references to .NET Standard.Library 1.6.1 from the tests though:
image

which does cause complaints from certain tooling.

@DanMcNamee42
Copy link
Author

Sorry I wasn't clear. It's with NuGet packages that are included in PdfPig. They could be packages that are pulling in other dependencies that are out of date. Looking at the NuGet packages that are in PdfPig now, all of them are out of date, with CodeCov being deprecated and no longer maintained. Possibly updating the NuGet packages will update the dependencies..

@Numpsy
Copy link
Contributor

Numpsy commented Feb 6, 2024

there's already a discussion about the coverage thing in #755

@DanMcNamee42
Copy link
Author

Thank you! Hopefully there will be a discussion about updating the other packages as well.

@Numpsy
Copy link
Contributor

Numpsy commented Feb 16, 2024

The dependencies in the test project have been updated and minimzed now, which has removed transitive references to a load of old stuff, though the test project itself still runs against .NET Core 2.1 as well as 6.0

@DanMcNamee42
Copy link
Author

Thank you!

@Numpsy
Copy link
Contributor

Numpsy commented May 6, 2024

I think all the old package have been cleared out or updated now - so is there anything left to do here?

@DanMcNamee42
Copy link
Author

It all looks great now. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants