Top issues
Detected Windows executable files that do not implement protection from integer based memory allocation overflow attacks.
Causes risk: outdated toolchains detected
hardening
Problem
Protection from integer-based memory allocation overflow attacks is a vulnerability mitigation implemented by the programming language compiler. It enables enforcement of memory allocation limits during code execution. This is achieved by instrumenting each memory allocation instance (through the programming language keyword 'new') and validating its parameters. Should an application try to allocate a maximum number of elements via a single call to 'new', the execution will be terminated. This vulnerability mitigation is designed to protect against resource exhaustion and improper handling of memory allocation failures.Prevalence in NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
3 packages
found in
Top 10k
1.01k packages
in community
Next steps
Microsoft VisualStudio users can take advantage of this configuration-free vulnerability mitigation by updating to a newer compiler version. With this update, additional vulnerability mitigation options will also become available.
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
1.09k 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.
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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.Prevalence in NuGet community
No prevalence information at this timeNext steps
Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.
Detected Windows executable files that trigger ASLR compatibility mode and reduce its effectiveness.
Causes risk: reduced effectiveness mitigations
hardening
Problem
Address Space Layout Randomization (ASLR) is a vulnerability mitigation option that forces software components to load on a different memory base address each time they are used. This mitigation is detected as enabled, but rendered ineffective since the set load base address forces the 64-bit image to load within the lower 32-bit memory range. Having a smaller memory range makes ASLR more predictable, and it is therefore easier for malicious code to bypass it.Prevalence in NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
6 packages
found in
Top 10k
1.16k packages
in community
Next steps
Review the programming language linker options.
In Microsoft VisualStudio, you should check if the linker option /BASE is set to a value lesser than 4GB.
Detected Windows executable files that do not implement CFG vulnerability mitigation protection.
Causes risk: modern mitigations missing
hardening
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. Because the code flow integrity is verified during runtime, malicious code is less likely to be able to hijack trusted execution paths.Prevalence in NuGet community
0 packages
found in
Top 100
2 packages
found in
Top 1k
38 packages
found in
Top 10k
9.4k 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.
Top behaviors
Requests permission required to perform restore operations.
permissions
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
1.47k packages
in community
Requests permission required to perform a number of security-related functions, such as controlling and viewing audit messages.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
21 packages
found in
Top 10k
1.43k packages
in community
Tampers with information in URL Zone Identifier, commonly used to bypass warnings after downloading files from the Internet.
settings
Prevalence in NuGet community
Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
6 packages
found in
Top 10k
463 packages
in community
Checks operating system version.
search
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
9 packages
found in
Top 1k
67 packages
found in
Top 10k
16.58k packages
in community
Opens registry keys.
registry
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
4 packages
found in
Top 1k
56 packages
found in
Top 10k
13.9k packages
in community
Top vulnerabilities
No vulnerabilities found.