Spectra Assure

warningRisk: Hardening

Scanned:

Verify.XunitV3

latest

Top 10k

License: Permissive (MIT)

New!

Published:

See on NuGet

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

7 debugging symbols found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

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

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.

Prevalence in NuGet community

0 packages

found in

Top 100

22 packages

found in

Top 1k

142 packages

found in

Top 10k

59.57k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

SQ14160

Detected Windows executable files that embed PDB files whose integrity is verified with an insecure hashing algorithm.

Causes risk: outdated toolchains detected

hardening

Problem

Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed-source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.

Prevalence in NuGet community

0 packages

found in

Top 100

14 packages

found in

Top 1k

69 packages

found in

Top 10k

19.61k packages

in community

Next steps

Private debug database files should not be embedded within executables, and you should remove them from the software package before releasing it.

The integrity verification of the embedded database files should not be done with insecure hashing algorithms. SHA1 and MD5 hashes should be deprecated throughout the application, and a more secure SHA256 algorithm should be used instead.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

4 packages

found in

Top 10k

1.09k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider rewriting the flagged code without using the marked behaviors.

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

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.

SQ34203

Detected presence of hardcoded debug databases.

Causes risk: debugging symbols found

secrets

Problem

Debug databases are typically only used during software development. On Windows, they are usually files embedded into the executable (PDB), while on Linux, they're contained inside special executable sections. The databases contain private debug symbols that make it significantly easier to reverse-engineer a closed-source application. In some cases, having a debug database is equivalent to having access to the source code. Presence of debug databases could indicate that one or more software components have been built using a debug profile, instead of the release. Private debug databases can be embedded into software components by programming language tools.

Prevalence in NuGet community

0 packages

found in

Top 100

15 packages

found in

Top 1k

76 packages

found in

Top 10k

21.58k packages

in community

Next steps

To remediate this issue and remove private debugging information, refer to your programming language toolchain documentation.

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

732.23k 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

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

22 packages

found in

Top 1k

142 packages

found in

Top 10k

59.57k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

SQ14160

Detected Windows executable files that embed PDB files whose integrity is verified with an insecure hashing algorithm.

Causes risk: outdated toolchains detected

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

14 packages

found in

Top 1k

69 packages

found in

Top 10k

19.61k packages

in community

Next steps

Private debug database files should not be embedded within executables, and you should remove them from the software package before releasing it.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

4 packages

found in

Top 10k

1.09k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider rewriting the flagged code without using the marked behaviors.

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

733.24k packages

in community

Next steps

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

SQ34203

Detected presence of hardcoded debug databases.

Causes risk: debugging symbols found

secrets

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

15 packages

found in

Top 1k

76 packages

found in

Top 10k

21.58k packages

in community

Next steps

To remediate this issue and remove private debugging information, refer to your programming language toolchain documentation.

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

732.23k packages

in community