Top issues
Detected presence of severe vulnerabilities with active exploitation.
Causes risk: actively exploited vulnerabilities
vulnerabilities
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
62067 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.
Detected presence of malware-exploited vulnerabilities.
Causes risk: malware exploited vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.Prevalence in NuGet community
0 packages
found in
Top 100
1 packages
found in
Top 1k
25 packages
found in
Top 10k
5061 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.
Detected presence of critical severity vulnerabilities.
Causes risk: critical severity vulnerabilities
vulnerabilities
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
21524 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.
Detected Windows executable files that do not implement the DEP vulnerability mitigation protection.
Causes risk: baseline mitigations missing
hardening
Problem
Data Execution Prevention (DEP/NX) is a vulnerability mitigation option that prevents data from being interpreted as code anywhere within the application. This mitigation protects the application stack, heap and other memory data ranges. Executable files that fail to implement this mitigation expose the user to increased risks of malicious code injection.Prevalence in NuGet community
0 packages
found in
Top 100
4 packages
found in
Top 1k
27 packages
found in
Top 10k
5912 packages
in community
Next steps
It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.
To enable this mitigation, refer to your programming language linker documentation.
In Microsoft VisualStudio, you can enable DEP mitigation by setting the linker option /NXCOMPAT to ON.
Detected Windows executable files compiled without following the SDL best practices while using banned string functions.
Causes risk: misconfigured toolchains detected
hardening
Problem
Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors. These checks prevent the use of hard-to-secure string manipulation functions. They enforce static memory access checks, and allow only the use of range-verified string parsing functions. While these checks do not prevent every memory corruption issue by themselves, they do help reduce the likelihood.Prevalence in NuGet community
0 packages
found in
Top 100
1 packages
found in
Top 1k
23 packages
found in
Top 10k
4708 packages
in community
Next steps
It's highly recommended to enable these checks for all software components used at security boundaries, or those that process user controlled inputs.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.
Top behaviors
Requests permission required to load or unload a device driver.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
12 packages
found in
Top 10k
863 packages
in community
Requests permission required to identify itself as a part of the trusted computer base.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
15 packages
found in
Top 10k
1059 packages
in community
Requests permission required to create a computer account.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
12 packages
found in
Top 10k
818 packages
in community
Requests permission required to access Credential Manager as a trusted caller.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
12 packages
found in
Top 10k
789 packages
in community
Retrieves the name of the user associated with the process.
search
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
4 packages
found in
Top 1k
70 packages
found in
Top 10k
23059 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(75 Active Vulnerabilities)
27 (27 Fixable)
CVE-2019-20388h
CVE-2019-20838h
CVE-2020-7595h
48 (48 Fixable)
CVE-2022-32221c
CVE-2022-37434c
CVE-2024-56171c
2 (2 Fixable)
CVE-2022-40304h
CVE-2022-40303h
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated