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

C#

Artifact:
latest
Top 100
Base language support for C#
License: unknown
Published: 12 days ago

Publisher: ms-dotnettools



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
11 debugging symbols found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
11 outdated toolchains detected

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

37.29M
Total Installs
Contributor
Declared Dependencies
69
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 Visual Studio Code community

22 packages
found in
Top 100
104 packages
found in
Top 1k
197 packages
found in
Top 10k
774 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 Visual Studio Code community

78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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

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. Each of these components can have dozens, or even hundreds, of its own dependencies. When building applications, software developers download and install components from public repositories. For components to work properly, all of their dependencies also need to be installed. Some package repositories, like Node Package Manager (NPM), allow components to declare dependencies that are hosted remotely. Such dependencies are automatically downloaded from a specified location during software component installation. Since remotely hosted dependencies are not immutable, that enables a threat actor to change the dependency contents even after a component was published and vetted by security solutions. It is uncommon to find open source components that use remotely hosted dependencies residing outside the official project source code repository.

Prevalence in Visual Studio Code community

35 packages
found in
Top 100
226 packages
found in
Top 1k
1137 packages
found in
Top 10k
5416 packages
in community

Next steps

Review software component remote dependency locations.
If the software component resolves dependencies from unusual locations, investigate the build and release environment for software supply chain compromise.
Consider vendoring the software component with all of its dependencies.
Avoid using this software package until it is vetted as safe.

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 Visual Studio Code community

38 packages
found in
Top 100
250 packages
found in
Top 1k
719 packages
found in
Top 10k
3448 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

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 Visual Studio Code community

5 packages
found in
Top 100
23 packages
found in
Top 1k
64 packages
found in
Top 10k
189 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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
8 packages
found in
Top 100
14 packages
found in
Top 1k
30 packages
found in
Top 10k
84 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
21 packages
found in
Top 100
135 packages
found in
Top 1k
319 packages
found in
Top 10k
1413 packages
in community

Prevalence in Visual Studio Code community

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

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
10 packages
found in
Top 100
52 packages
found in
Top 1k
151 packages
found in
Top 10k
724 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
10 packages
found in
Top 100
40 packages
found in
Top 1k
68 packages
found in
Top 10k
471 packages
in community

Top vulnerabilities

No vulnerabilities found.