Spectra Assure
Community
Docs
failRisk: Vulnerabilities
Scanned: 3 days ago

runtime.win10-x64.Microsoft.NETCore.UniversalWindowsPlatform

latest
Top 10k
Internal implementation package not meant for direct consumption. Please do not reference directly. Provides a set of packages that can be used when building Universal Windows applications on .NETCore. d67bd83a075b8b10cb95810568073c1a3211f28b When using NuGet 3.x this package requires at least version 3.4.
License: unknown
Published: over 3 years ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
2 severe vulnerabilities exploited
Hardening
1 misconfigured toolchains detected

Threats

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

Popularity

9.07M
Total Downloads
Contributors
Declared Dependencies
0
Dependents

Top 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
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.

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.

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
88612 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

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.

Prevalence in NuGet community

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

Next steps

You should keep the debug table to prove that the SDL process has been followed.
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.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in NuGet community

No prevalence information at this time

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Top behaviors

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

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

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

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

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
(2 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2022-37434c
CVE-2018-25032h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated