Spectra Assure
Community
warningRisk: Secrets
Scanned: 13 days ago

runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver

latest
Top 10k
Internal implementation package not meant for direct consumption. Please do not reference directly. Provides an implementation of framework resolution strategy used by Microsoft.NETCore.DotNetHost When using NuGet 3.x this package requires at least version 3.4.
License: unknown
Published: over 6 years ago
See on NuGet

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 debugging symbols found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
1 execution hijacking concerns

Threats

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

Popularity

19.54M
Total Downloads
2
Contributors
1
Declared Dependencies
0
Dependents

Top issues

See all issues

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.

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

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.

Problem

On Linux, external symbols are resolved via the procedure linkage table (PLT) and the global offset table (GOT). Without any protection, both are writable at runtime and thus leave the executable vulnerable to pointer hijacking - an attack where the function address is overwritten with an address of a malicious function. Pointer hijacking can be mitigated by using full read-only relocations, which instruct the compiler to unify global offset tables into a single read-only table. This requires that all external function symbols are resolved at load-time instead of during execution, and may increase loading time for large programs.

Prevalence in NuGet community

0 packages
found in
Top 100
1 packages
found in
Top 1k
24 packages
found in
Top 10k
4.43k packages
in community

Next steps

In most cases, it's recommended to use full read-only relocations (in GCC: -Wl,-z,relro,-z,now).
If the executable load-time is an issue, you should use partial read-only relocations.

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.

Prevalence in NuGet community

0 packages
found in
Top 100
38 packages
found in
Top 1k
315 packages
found in
Top 10k
733.24k packages
in community

Next steps

Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.
With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

Problem

Common compilers often embed source code information into executables for debugging purposes, usually by mapping symbols to source filenames or paths. While this is typically desirable in open-source software and standard tools, that information can be used to determine security weaknesses, code repository layout, trade secrets and similar sensitive information. Such symbols make it easier to reverse-engineer a closed source application.

Prevalence in NuGet community

0 packages
found in
Top 100
1 packages
found in
Top 1k
23 packages
found in
Top 10k
4.62k packages
in community

Next steps

Strip out such information in the linking phase by using compiler options like the -s flag in GCC, or in the post-build phase by using the strip tool.

Top behaviors

See all behaviors

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
560.29k packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
63 packages
found in
Top 1k
513 packages
found in
Top 10k
735.91k packages
in community

Prevalence in NuGet community

No behavior prevalence information at this time

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
26 packages
found in
Top 1k
213 packages
found in
Top 10k
99.98k packages
in community

Prevalence in NuGet community

Behavior often found in this community (Common)
0 packages
found in
Top 100
8 packages
found in
Top 1k
93 packages
found in
Top 10k
34.83k packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver

What is runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver?

Internal implementation package not meant for direct consumption. Please do not reference directly. Provides an implementation of framework resolution strategy used by Microsoft.NETCore.DotNetHost When using NuGet 3.x this package requires at least version 3.4. For more information about this package, visit its homepage.

Is runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver malicious or is it safe to use?

The .NET package runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver 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.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver popular?

The .NET package runtime.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver ranks among the top 10000 projects in this community. It has 20M 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.ubuntu.14.04-x64.Microsoft.NETCore.DotNetHostResolver once it is in my app?

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