Spectra Assure
Community
Docs
warningRisk: Vulnerabilities
Scanned: 4 days ago

C/C++

Artifact:
C/C++ IntelliSense, debugging, and code browsing.
License: unknown
Published: 4 days ago

Publisher: ms-vscode



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
2 debugging symbols found

Security

Vulnerabilities
9 high severity vulnerabilities
Hardening
8 reduced effectiveness mitigations

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

91.95M
Total Installs
Contributor
Declared Dependencies
183
Dependents

Top issues

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 Visual Studio Code community

22 packages
found in
Top 100
104 packages
found in
Top 1k
197 packages
found in
Top 10k
774 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.

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

72 packages
found in
Top 100
583 packages
found in
Top 1k
3344 packages
found in
Top 10k
17282 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

Operating systems execute application code in multiple privilege access levels. Separation of privileges is designed to protect the stability and integrity of the operating system by shielding it from issues that the user run applications may cause. However, some users may need to interact with higher privilege parts of the operating system to accomplish specific tasks. For this purpose, operating systems provide facilities that users may leverage to temporarily elevate their running privileges. Users with higher privileges can run any application with the same privilege level as their own. Attackers often try to trick privileged users into running malicious code, enabling them to infect the operating system. While the presence of code that elevates user privileges does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that can elevate user privileges. One example of acceptable use for such functions is allowing the users to install software packages and updates.

Prevalence in Visual Studio Code community

29 packages
found in
Top 100
169 packages
found in
Top 1k
380 packages
found in
Top 10k
1338 packages
in community

Next steps

Investigate reported detections as indicators of software tampering.
Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.
Consider rewriting the flagged code without using the marked behaviors.

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

78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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.

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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
8 packages
found in
Top 100
14 packages
found in
Top 1k
30 packages
found in
Top 10k
84 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
21 packages
found in
Top 100
135 packages
found in
Top 1k
319 packages
found in
Top 10k
1413 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
9 packages
found in
Top 100
63 packages
found in
Top 1k
169 packages
found in
Top 10k
819 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
10 packages
found in
Top 100
52 packages
found in
Top 1k
151 packages
found in
Top 10k
724 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
10 packages
found in
Top 100
40 packages
found in
Top 1k
68 packages
found in
Top 10k
471 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(9 Active Vulnerabilities)
9 (9 Fixable)
CVE-2025-21176h
CVE-2024-38229h
CVE-2025-26646h
None
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated