Top issues
Detected Windows executable files compiled without following the SDL best practices while using banned string functions.
Causes risk: misconfigured toolchains detected
hardening
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 NuGet community
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 23 packages
found in 
Top 10k
 4708 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.
Detected Windows executable files with imported functions susceptible to pointer hijacking.
Causes risk: execution hijacking concerns
hardening
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 NuGet community
0 packages
found in 
Top 100
 2 packages
found in 
Top 1k
 12 packages
found in 
Top 10k
 3642 packages
in community
Next steps
Review the programming language linker options, and consider a build toolchain update.
Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.
Causes risk: execution hijacking concerns
hardening
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 NuGet community
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 11 packages
found in 
Top 10k
 2272 packages
in community
Next steps
Review the programming language linker options, and consider a build toolchain update.
Detected Windows executable files that were compiled without following the recommended SDL process.
Causes risk: misconfigured toolchains detected
hardening
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 NuGet community
0 packages
found in 
Top 100
 3 packages
found in 
Top 1k
 47 packages
found in 
Top 10k
 13120 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.
Detected Windows executable files compiled without following the SDL best practices while using banned memory functions.
Causes risk: misconfigured toolchains detected
hardening
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 NuGet community
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 14 packages
found in 
Top 10k
 4892 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.
Top behaviors
Sends data on a connected TCP socket.
network
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 0 packages
found in 
Top 1k
 23 packages
found in 
Top 10k
 9178 packages
in community
Receives data from a connected TCP socket.
network
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 0 packages
found in 
Top 1k
 22 packages
found in 
Top 10k
 8217 packages
in community
Permits an incoming connection on a TCP socket.
network
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 0 packages
found in 
Top 1k
 19 packages
found in 
Top 10k
 6621 packages
in community
Opens a socket listening for an incoming connection.
network
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 27 packages
found in 
Top 10k
 8912 packages
in community
Deletes files in Windows system directories.
file
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 3 packages
found in 
Top 1k
 48 packages
found in 
Top 10k
 10351 packages
in community
Top vulnerabilities
No vulnerabilities found.