Top issues
Detected presence of software components distributed with copyleft licenses.
Causes risk: copyleft licensed components
licenses
Problem
Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Copyleft licenses in particular impose substantial restrictions on the licensee. They typically require that any derived works, and even software code that merely interacts with copyleft code, be licensed under the same license. Since copyleft licenses are commonly applied to open source code, their inclusion requires that the entire software package becomes open sourced. For commercial applications, this is typically undesirable. Therefore, the inclusion of copyleft code is commonly avoided or even prohibited by the organization policy.Prevalence in Visual Studio Code community
6 packages
found in
Top 100
80 packages
found in
Top 1k
698 packages
found in
Top 10k
4351 packages
in community
Next steps
Confirm that the software package includes a copyleft component.
Investigate if the software publisher provides this component under a non-copyleft license.
Consider replacing the software component with an alternative that offers a license compatible with commercial use.
Detected presence of licenses that place restrictions on software distribution.
Causes risk: software distribution restrictions
licenses
Problem
Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.Prevalence in Visual Studio Code community
28 packages
found in
Top 100
205 packages
found in
Top 1k
1199 packages
found in
Top 10k
6212 packages
in community
Next steps
Confirm that the software package references a component or a dependency with a restrictive license.
Consider replacing the software component with an alternative that offers a license compatible with organization policy.
Detected Windows executable files that do not implement the safe exception handling vulnerability mitigation protection.
Causes risk: baseline mitigations missing
hardening
Problem
Safe Exception Handling (/SAFESEH) protects the code flow integrity by ensuring that exceptions are handled only by vetted functions. This mitigation protects dynamically constructed exception chains by checking the function targets prior to their execution. Because the code flow integrity is verified during runtime, malicious code is less likely to be able to hijack trusted execution paths. It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs. However, this option is only effective on systems that dynamically resolve exception handlers. Most notably, this option is recommended for 32-bit Windows applications that target the Intel x86 platform. Other operating system and platform combinations mitigate exception hijacking risks through the use of statically generated read-only tables.Prevalence in Visual Studio Code community
1 packages
found in
Top 100
8 packages
found in
Top 1k
27 packages
found in
Top 10k
88 packages
in community
Next steps
To enable this mitigation, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable safe exception handling mitigation by passing the /SAFESEH parameter to the linker.
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 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.
Detected Linux executable files that might set writable and executable permissions to the code segment, making non-executable memory mitigations less effective.
Causes risk: ineffective mitigations detected
hardening
Problem
Presence of code relocations indicates that the code segment might temporarily, at one point, become both writable and executable. That violates security policies adopted by most modern Linux distributions. During the brief period in which the code segment is both writable and executable, the attacker may be able to overwrite the code with a malicious program.Prevalence in Visual Studio Code community
3 packages
found in
Top 100
19 packages
found in
Top 1k
38 packages
found in
Top 10k
121 packages
in community
Next steps
Code relocations often appear due to inadequately written inline assembly, or when programs are not compiled with the appropriate position-independent code flag (e.g. -fPIC). In most cases, manual inspection may be required.
Top behaviors
Contains strings found in a Lua script interpreter.
execution
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
3 packages
found in
Top 1k
26 packages
found in
Top 10k
94 packages
in community
Queries the passwd database entry for a given user ID.
steal
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
31 packages
found in
Top 100
188 packages
found in
Top 1k
457 packages
found in
Top 10k
1719 packages
in community
Changes the value of a registry key.
registry
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
13 packages
found in
Top 100
77 packages
found in
Top 1k
235 packages
found in
Top 10k
1028 packages
in community
Opens URLs during installation or upon launch.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
47 packages
found in
Top 100
303 packages
found in
Top 1k
1634 packages
found in
Top 10k
8176 packages
in community
Contains URLs that link to interesting file formats.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
61 packages
found in
Top 100
477 packages
found in
Top 1k
2617 packages
found in
Top 10k
15022 packages
in community
Top vulnerabilities
No vulnerabilities found.