microsoft / microsoft/sqlmanagementobjects

Some Dependencies are flagged as vulnerable

Open
#179 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
143
Forks
28
PR merge metrics
No merged PRs in 30d

Description

I've only noticed this after the folks at github updated their github action windows runners to use a version of visual studio that has the NuGetAuditMode set to 'all', when the default used to be 'direct'. This means that any transitive Packages with security vulnerabilities are now flagged up as warnings, when previously you'd not see anything if you had -warnaserror set.

The following dependencies of sqlmanagementobjects are flagged as vulnerable, but I'd also like to highlight that a lot of the dependencies referenced in general are massively out of date:

Azure.Identity 1.10.3 (Latest 1.13.1)
Microsoft.Identity.Client 4.56.0 (Latest 4.66.2)
Microsoft.IdentityModel.JsonWebTokens 6.24.0 (Latest 8.2.1)
System.Formats.Asn1 5.0.0 (Latest 9.0.0)
System.IdentityModel.Tokens.Jwt 6.24.0 (latest 8.2.1)

At the moment, I've had to go through my projects and set the nugetauditmode back to direct to replicate the original behaviour so we have our builds back up and running - but obviously we can't stay in this mode forever, especially with a known security issue.

Are there any plans to update the dependencies for sqlmanagementobjects, or am I better off just trying to find an alternative?

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the dependency declarations for sqlmanagementobjects and review how the GitHub Actions Windows runner builds the project with NuGetAuditMode set to all. Update the vulnerable dependencies if compatible, then run the project build with transitive auditing enabled; done means the build succeeds without the reported vulnerability warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, github-actions
Domain
build-system, ci-cd, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.