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 medium severity vulnerabilities.
Causes risk: medium 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 medium severity.Prevalence in Visual Studio Code community
64 packages
found in
Top 100
530 packages
found in
Top 1k
2998 packages
found in
Top 10k
16.52k 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.
Detected presence of plaintext credentials within network protocol strings.
Causes risk: web service credentials found
secrets
Problem
Various network communication protocols allow including plaintext authentication credentials. Information such as user names and passwords could be passed through a non-encrypted channel, and therefore intercepted by malicious actors. Credentials are considered secrets, and should be kept encrypted until they are used. This policy control matches the following URI pattern protocol://username:password@domain within any software package component.Prevalence in Visual Studio Code community
14 packages
found in
Top 100
112 packages
found in
Top 1k
273 packages
found in
Top 10k
1.71k packages
in community
Next steps
Review the reported matches. If the warning refers to a placeholder credential value, it can be safely ignored.
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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.Prevalence in Visual Studio Code community
79 packages
found in
Top 100
560 packages
found in
Top 1k
2912 packages
found in
Top 10k
17.75k 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 changing the port to one that is standard for the networking protocol.
Top behaviors
Modifies file/directory permissions.
permissions
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
67 packages
found in
Top 100
547 packages
found in
Top 1k
2891 packages
found in
Top 10k
14.99k packages
in community
Might contain potentially obfuscated code or data.
anomaly
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
84 packages
found in
Top 100
679 packages
found in
Top 1k
4393 packages
found in
Top 10k
30.42k packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
82 packages
found in
Top 100
636 packages
found in
Top 1k
3971 packages
found in
Top 10k
25.82k packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
74 packages
found in
Top 100
578 packages
found in
Top 1k
3262 packages
found in
Top 10k
18.65k packages
in community
Contains a sequence of bytes that can be decoded into a printable string.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
54 packages
found in
Top 100
378 packages
found in
Top 1k
1783 packages
found in
Top 10k
7.78k packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(4 Active Vulnerabilities)
2 (2 Fixable)
CVE-2024-11023m
CVE-2024-43796m
2 (2 Fixable)
CVE-2024-7042c
CVE-2024-7774c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated