Spectra Assure

warningRisk: Hardening

Scanned:

Microsoft.CodeCoverage

latest

Top 1k

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 execution hijacking concerns

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

Buffer overrun protection on Linux is achieved in two ways. The most common solution is to use the stack canary (also called cookie). The stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. In most cases, compilers will apply the stack canary conservatively in order to avoid a negative performance impact. Therefore, stack canaries are often used together with another stack overrun mitigation - fortified functions. Fortified functions are usually wrappers around standard glibc functions (such as memcpy) which perform boundary checks either at compile time or run time to determine if a memory violation has occurred. The compiler needs additional context to generate such calls (for example, array size that needs to be known at compile time). Because of this, the compiler will virtually never substitute all viable functions with their fortified counterparts in complex programs. However, when combined with the stack canary, fortified functions provide a good measure of buffer overrun protection.

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

17 packages

found in

Top 10k

2228 packages

in community

Next steps

Presence of unfortified string functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

SQ18106

Detected Linux executable files compiled without any kind of buffer overrun protection while using banned memory functions.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

19 packages

found in

Top 10k

2641 packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

SQ18107

Detected Linux executable files compiled without any kind of buffer overrun protection while using banned input functions.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

19 packages

found in

Top 10k

2224 packages

in community

Next steps

Presence of some input functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

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

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

SQ18113

Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.

Causes risk: execution hijacking concerns

hardening

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

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

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.

SQ18108

Detected Linux executable files without any fortified functions.

Causes risk: low priority mitigations absent

hardening

Problem

Fortified functions are usually wrappers around standard glibc functions (such as memcpy) which perform boundary checks either at compile time or run time to determine if a memory violation has occurred. The compiler needs additional context to generate such calls (for example, array size that needs to be known at compile time). Because of this, the compiler will virtually never substitute all viable functions with their fortified counterparts in complex programs. However, lack of any fortified functions may indicate that this compiler feature was not used at all.

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

22 packages

found in

Top 10k

4342 packages

in community

Next steps

In GCC, you can enable fortified functions with -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

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.

TH16126

Detected presence of software components that can access user identity information.

hunting

Problem

Operating systems allow multiple user accounts to coexist on a single computer system. Each registered user has identity information associated with their account. At the very least, user accounts consist of a user name and an optional password. In some cases, user account data may also include personally identifiable information. Extended personal information may include user's given and last name, their email and mailing address, personal photo and their telephone number. Financially motivated attackers may seek to collect personal information for purposes of selling the private data to a third-party. Malicious code that typically exhibits these behavior traits is commonly referred to as an information stealer. While the presence of code that accesses identity information does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Accessing identity information is a very common behavior for software packages. One example of acceptable use for such functions is verifying that the active user has purchased a software license that allows them to run the application.

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

27 packages

found in

Top 10k

4144 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

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

1 packages

found in

Top 1k

17 packages

found in

Top 10k

2228 packages

in community

Next steps

Presence of unfortified string functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

SQ18106

Detected Linux executable files compiled without any kind of buffer overrun protection while using banned memory functions.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

19 packages

found in

Top 10k

2641 packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

SQ18107

Detected Linux executable files compiled without any kind of buffer overrun protection while using banned input functions.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

19 packages

found in

Top 10k

2224 packages

in community

Next steps

Presence of some input functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

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

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

SQ18113

Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.

Causes risk: execution hijacking concerns

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

24 packages

found in

Top 10k

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

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.

SQ18108

Detected Linux executable files without any fortified functions.

Causes risk: low priority mitigations absent

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

22 packages

found in

Top 10k

4342 packages

in community

Next steps

In GCC, you can enable fortified functions with -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

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

Next steps

TH16126

Detected presence of software components that can access user identity information.

hunting

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

1 packages

found in

Top 1k

27 packages

found in

Top 10k

4144 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.