Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 13 days ago

Nerdbank.GitVersioning

latest
Top 10k
Stamps your assemblies with semver 2.0 compliant git commit specific version information and provides NuGet versioning information as well.
License: Permissive (MIT)
Published: 2 months ago
See on NuGet

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
15 debugging symbols found

Security

Vulnerabilities
4 severe vulnerabilities exploited
Hardening
2 reduced effectiveness mitigations

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

25.63M
Total Downloads
5
Contributors
0
Declared Dependencies
134
Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in NuGet community

0 packages
found in
Top 100
4 packages
found in
Top 1k
86 packages
found in
Top 10k
62.07k packages
in community

Next steps

We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.

Prevalence in NuGet community

0 packages
found in
Top 100
3 packages
found in
Top 1k
47 packages
found in
Top 10k
21.52k packages
in community

Next steps

Perform impact analysis for the reported CVEs.
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in NuGet community

0 packages
found in
Top 100
4 packages
found in
Top 1k
115 packages
found in
Top 10k
88.61k packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.

Prevalence in NuGet community

0 packages
found in
Top 100
22 packages
found in
Top 1k
142 packages
found in
Top 10k
59.57k packages
in community

Next steps

Investigate reported detections.
If the software should not include these network references, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider an alternative delivery mechanism for software packages.

Problem

Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed-source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.

Prevalence in NuGet community

0 packages
found in
Top 100
14 packages
found in
Top 1k
69 packages
found in
Top 10k
19.61k packages
in community

Next steps

Private debug database files should not be embedded within executables, and you should remove them from the software package before releasing it.
The integrity verification of the embedded database files should not be done with insecure hashing algorithms. SHA1 and MD5 hashes should be deprecated throughout the application, and a more secure SHA256 algorithm should be used instead.

Top behaviors

See all behaviors

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
3 packages
found in
Top 1k
48 packages
found in
Top 10k
10.35k packages
in community

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
23 packages
found in
Top 10k
3.08k packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
144 packages
found in
Top 10k
69.16k packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
133 packages
found in
Top 10k
60.64k packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
22 packages
found in
Top 1k
142 packages
found in
Top 10k
59.98k packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(5 Active Vulnerabilities)
1 (1 Fixable)
CVE-2022-1586c
4 (4 Fixable)
CVE-2016-3191c
CVE-2017-8399c
CVE-2017-8786c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Nerdbank.GitVersioning

What is Nerdbank.GitVersioning?

Stamps your assemblies with semver 2.0 compliant git commit specific version information and provides NuGet versioning information as well. For more information about this package, visit its homepage.

Is Nerdbank.GitVersioning malicious or is it safe to use?

The .NET package Nerdbank.GitVersioning was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is Nerdbank.GitVersioning popular?

The .NET package Nerdbank.GitVersioning ranks among the top 10000 projects in this community. It has 26M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure Nerdbank.GitVersioning once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Nerdbank.GitVersioning behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Nerdbank.GitVersioning version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.