Spectra Assure
Community
Docs
warningRisk: Hardening
Scanned: 8 days ago

WindowsUtils

latest
Top 10k
This module contains tools to facilitate the administration of Windows computers.
License: unknown
Published: 11 months ago




SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 debugging symbols 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

Popularity

43.67k
Total Downloads
Contributors
Declared Dependencies
0
Dependents

Top issues

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 PowerShell Gallery community

1 packages
found in
Top 100
22 packages
found in
Top 1k
87 packages
found in
Top 10k
171 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

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 PowerShell Gallery community

7 packages
found in
Top 100
389 packages
found in
Top 1k
1464 packages
found in
Top 10k
2513 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.

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 PowerShell Gallery community

3 packages
found in
Top 100
39 packages
found in
Top 1k
188 packages
found in
Top 10k
322 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 PowerShell Gallery community

1 packages
found in
Top 100
14 packages
found in
Top 1k
43 packages
found in
Top 10k
86 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

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 PowerShell Gallery community

3 packages
found in
Top 100
108 packages
found in
Top 1k
239 packages
found in
Top 10k
423 packages
in community

Next steps

Remove private debug database files from the software package before you release it.

Top behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
12 packages
found in
Top 100
172 packages
found in
Top 1k
803 packages
found in
Top 10k
1281 packages
in community

Prevalence in PowerShell Gallery community

Behavior uncommon for this community (Uncommon)
1 packages
found in
Top 100
22 packages
found in
Top 1k
63 packages
found in
Top 10k
100 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
2 packages
found in
Top 100
23 packages
found in
Top 1k
66 packages
found in
Top 10k
105 packages
in community

Prevalence in PowerShell Gallery community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
37 packages
found in
Top 1k
184 packages
found in
Top 10k
303 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
5 packages
found in
Top 100
66 packages
found in
Top 1k
509 packages
found in
Top 10k
748 packages
in community

Top vulnerabilities

No vulnerabilities found.