Spectra Assure

warningRisk: Hardening

Scanned:

clipboardy

latest

Top 10k

Access the system clipboard (copy/paste)

License: Permissive (MIT)

Published:

Visit GitHub

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

2 debugging symbols found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

1 baseline mitigations missing

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

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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

33 packages

found in

Top 10k

4.37k 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 npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

41 packages

found in

Top 10k

8.21k packages

in community

Next steps

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

Problem

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Thread local storage (TLS) callbacks are pointers to code initialization and resource release functions. 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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

28 packages

found in

Top 10k

5.52k packages

in community

Next steps

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

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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

69 packages

found in

Top 10k

11.39k 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.

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 memory manipulation functions. They enforce static memory access checks, and allow only the use of range-verified memory access functions. While these checks do not prevent every memory corruption issue by themselves, they do help reduce the likelihood.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

29 packages

found in

Top 10k

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

ASLR (address-space layout randomization) is a mitigation technique that increases the difficulty of performing buffer-overflow attacks that require the attacker to know the address of the program in memory. This is done by loading the program at a randomly selected address in the process' address space. ASLR-enabled kernels can choose a random load address only for position-independent executables and code.

Prevalence in npm community

0 packages

found in

Top 100

2 packages

found in

Top 1k

53 packages

found in

Top 10k

8.46k packages

in community

Next steps

To support ASLR, the program must be compiled as position-independent code. In most compilers, this is done by passing the corresponding position-independent flag, such as -fPIC for shared libraries or -fPIE for executables.

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

73 packages

found in

Top 10k

14.3k 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.

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 npm community

0 packages

found in

Top 100

2 packages

found in

Top 1k

101 packages

found in

Top 10k

17.12k 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.

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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

79 packages

found in

Top 10k

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

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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

93 packages

found in

Top 10k

9.46k packages

in community

Next steps

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

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.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

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

Policies

Info

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

33 packages

found in

Top 10k

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

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

41 packages

found in

Top 10k

8.21k packages

in community

Next steps

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

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

28 packages

found in

Top 10k

5.52k packages

in community

Next steps

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

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

69 packages

found in

Top 10k

11.39k 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.

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

29 packages

found in

Top 10k

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

Prevalence in npm community

0 packages

found in

Top 100

2 packages

found in

Top 1k

53 packages

found in

Top 10k

8.46k packages

in community

Next steps

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

73 packages

found in

Top 10k

14.3k 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.

Problem

Prevalence in npm community

0 packages

found in

Top 100

2 packages

found in

Top 1k

101 packages

found in

Top 10k

17.12k 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.

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

79 packages

found in

Top 10k

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

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

93 packages

found in

Top 10k

9.46k packages

in community

Next steps

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

clipboardy

SAFE Assessment

Compliance

Security

Threats

SQ14140Detected Windows executable files compiled without following the SDL best practices while using banned string functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ14156Detected Windows executable files with imported functions susceptible to pointer hijacking.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ14158Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ14138Detected Windows executable files that were compiled without following the recommended SDL process.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ14139Detected Windows executable files compiled without following the SDL best practices while using banned memory functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ18111Detected Linux executable files that do not implement the ASLR vulnerability mitigation protection.Causes risk: baseline mitigations missinghardening

Problem

Prevalence in npm community

Next steps

SQ14122Detected Windows executable files that do not implement CFG vulnerability mitigation protection.Causes risk: modern mitigations missinghardening

Problem

Prevalence in npm community

Next steps

SQ14127Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.Causes risk: low priority mitigations absenthardening

Problem

Prevalence in npm community

Next steps

SQ18113Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ34203Detected presence of hardcoded debug databases.Causes risk: debugging symbols foundsecrets

Problem

Prevalence in npm community

Next steps

Did you know...

SQ14140Detected Windows executable files compiled without following the SDL best practices while using banned string functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ14156Detected Windows executable files with imported functions susceptible to pointer hijacking.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ14158Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ14138Detected Windows executable files that were compiled without following the recommended SDL process.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ14139Detected Windows executable files compiled without following the SDL best practices while using banned memory functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ18111Detected Linux executable files that do not implement the ASLR vulnerability mitigation protection.Causes risk: baseline mitigations missinghardening

Problem

Prevalence in npm community

Next steps

SQ14122Detected Windows executable files that do not implement CFG vulnerability mitigation protection.Causes risk: modern mitigations missinghardening

Problem

Prevalence in npm community

Next steps

SQ14127Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.Causes risk: low priority mitigations absenthardening

Problem

Prevalence in npm community

Next steps

SQ18113Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.Causes risk: execution hijacking concernshardening

Problem