Spectra Assure

warningRisk: Hardening

Scanned:

Microsoft.NET.Workload.Emscripten.net7.Manifest-8.0.100.Msi.x64

Top 1k

Internal toolchain package not meant for direct consumption. Please do not reference directly.

License: Permissive (MIT)

Published:

See on NuGet

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

3 misconfigured toolchains detected

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

List of software quality issues with the number of affected components.

Policies

Info

Count

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.

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

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.

SQ14125

Detected Windows shared library files that do not suppress exports which reduces CFG vulnerability mitigation protection effectiveness.

Causes risk: low priority mitigations absent

hardening

Problem

Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that dynamic calls are made only to vetted functions. Trusted execution paths rely on the ability of the operating system to build a list of valid function targets. Certain functions can intentionally be disallowed to prevent malicious code from deactivating vulnerability mitigation features. A list of such invalid function targets can include publicly exported symbols. Applications that enhance control flow integrity through export suppression rely on libraries to mark their publicly visible symbols as suppressed. This is done for all symbols that are considered to be sensitive functions, and to which access should be restricted. It is considered dangerous to mix applications that perform export suppression with libraries that do not.

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

49 packages

found in

Top 10k

15484 packages

in community

Next steps

To enable this mitigation on library code, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that indirect calls are made only to vetted functions. This mitigation protects dynamically resolved function targets by instrumenting the code responsible for transferring execution control. Higher-level programming languages implement structured exception handling by managing their own code flow execution paths. As such, they are subject to code flow hijacking during runtime. Language-specific exception handling mitigation enforces execution integrity by instrumenting calls to manage execution context switching. Any deviation from the known and trusted code flow paths will cause the application to terminate. This makes malicious code less likely to execute.

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

16146 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 toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ20119

Detected digital signatures that rely on a weak digest algorithm for integrity validation.

signatures

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

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

SQ20121

Detected digital signatures that have not been performed with an extended validation certificate.

signatures

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be purchased from certificate authorities or be self-issued. When a certificate is purchased from a certificate authority, the subject that requests it goes through an identity validation process. Depending on the certificate type, those checks can be basic or extended. Confirming the subject identity is a multi-step process, and the requesting subject can be mapped to its legal entity name only through extended validation of submitted documents. Extended identity validation typically costs more, and it takes longer for a certificate to be issued when this process is correctly followed.

Prevalence in NuGet community

0 packages

found in

Top 100

27 packages

found in

Top 1k

292 packages

found in

Top 10k

732229 packages

in community

Next steps

Consider the benefits of acquiring extended validation certificates. Operating systems tend to be more trusting of software packages signed in this way. Certain security warnings and prompts might also be automatically suppressed. This reduces the number of support tickets for organizations that opt to use extended validation certificates.

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.

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

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.

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

Problem

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.

SQ14125

Detected Windows shared library files that do not suppress exports which reduces CFG vulnerability mitigation protection effectiveness.

Causes risk: low priority mitigations absent

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

49 packages

found in

Top 10k

15484 packages

in community

Next steps

To enable this mitigation on library code, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

16146 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 toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ20119

Detected digital signatures that rely on a weak digest algorithm for integrity validation.

signatures

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

38 packages

found in

Top 1k

315 packages

found in

Top 10k

733240 packages

in community

Next steps

With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

SQ20121

Detected digital signatures that have not been performed with an extended validation certificate.

signatures

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

27 packages

found in

Top 1k

292 packages

found in

Top 10k

732229 packages

in community