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

runtime.win10-arm.Microsoft.Net.Native.Compiler

latest
Top 10k
.Net Native Compilers package. Referencing this package will cause the project to be built using the specific version of the .NET Native compiler contained in the package, as opposed to any system installed version. Supported Platforms: - UWP tools 2.2
License: unknown
Published: almost 7 years ago
See on NuGet

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
23 debugging symbols found

Security

Vulnerabilities
6 severe vulnerabilities exploited
Hardening
28 reduced effectiveness mitigations

Threats

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

Popularity

8.04M
Total Downloads
2
Contributors
1
Declared Dependencies
2
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
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

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.

Problem

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Imported function addresses are pointers to the symbols that implement the application-required functionality. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.

Prevalence in NuGet community

0 packages
found in
Top 100
2 packages
found in
Top 1k
12 packages
found in
Top 10k
3642 packages
in community

Next steps

Review the programming language linker options, and consider a build toolchain update.

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.

Top behaviors

See all behaviors

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

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
26 packages
found in
Top 10k
6500 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
15 packages
found in
Top 10k
2302 packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
62 packages
found in
Top 1k
484 packages
found in
Top 10k
560289 packages
in community

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
10351 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(6 Active Vulnerabilities)
None
6 (6 Fixable)
CVE-2016-9841c
CVE-2016-9843c
CVE-2022-37434c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for runtime.win10-arm.Microsoft.Net.Native.Compiler

What is runtime.win10-arm.Microsoft.Net.Native.Compiler?

.Net Native Compilers package. Referencing this package will cause the project to be built using the specific version of the .NET Native compiler contained in the package, as opposed to any system installed version. Supported Platforms: - UWP tools 2.2. For more information about this package, visit its homepage.

Is runtime.win10-arm.Microsoft.Net.Native.Compiler malicious or is it safe to use?

The .NET package runtime.win10-arm.Microsoft.Net.Native.Compiler 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 runtime.win10-arm.Microsoft.Net.Native.Compiler popular?

The .NET package runtime.win10-arm.Microsoft.Net.Native.Compiler ranks among the top 10000 projects in this community. It has 8M 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 runtime.win10-arm.Microsoft.Net.Native.Compiler once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how runtime.win10-arm.Microsoft.Net.Native.Compiler behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a runtime.win10-arm.Microsoft.Net.Native.Compiler 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.