Top issues
Detected presence of severe vulnerabilities with active exploitation.
Causes risk: actively exploited vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.Prevalence in Visual Studio Code community
67 packages
found in
Top 100
548 packages
found in
Top 1k
3078 packages
found in
Top 10k
17.39k packages
in community
Next steps
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected presence of critical severity vulnerabilities.
Causes risk: critical severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.Prevalence in Visual Studio Code community
60 packages
found in
Top 100
453 packages
found in
Top 1k
2271 packages
found in
Top 10k
12.07k packages
in community
Next steps
Perform impact analysis for the reported CVEs.
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected presence of high severity vulnerabilities.
Causes risk: high severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.Prevalence in Visual Studio Code community
68 packages
found in
Top 100
555 packages
found in
Top 1k
3086 packages
found in
Top 10k
17.47k packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
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
79 packages
found in
Top 100
622 packages
found in
Top 1k
4233 packages
found in
Top 10k
29.36k 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.
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
7 packages
found in
Top 100
79 packages
found in
Top 1k
735 packages
found in
Top 10k
4.58k 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.
Top behaviors
Downloads files in silent mode via HTTP.
network
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
4 packages
found in
Top 1k
16 packages
found in
Top 10k
52 packages
in community
Contains URLs that link to raw files on GitHub.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
79 packages
found in
Top 100
622 packages
found in
Top 1k
4233 packages
found in
Top 10k
29.36k 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)
59 packages
found in
Top 100
488 packages
found in
Top 1k
2687 packages
found in
Top 10k
15.88k packages
in community
Executes files during installation or upon launch.
execution
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
94 packages
found in
Top 100
837 packages
found in
Top 1k
6746 packages
found in
Top 10k
87.76k packages
in community
Contains URLs with suspicious path components.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
39 packages
found in
Top 100
249 packages
found in
Top 1k
1058 packages
found in
Top 10k
5.33k packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(9 Active Vulnerabilities)
8 (8 Fixable)
CVE-2021-41116c
CVE-2024-51736c
CVE-2022-24828h
1 (1 Fixable)
CVE-2021-29472h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated