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

文心快码 ( Baidu Comate )

Artifact:
latest
Top 10k
Coding mate, Pair you create. Your AI Coding Assistant with Autocomplete & Chat for Java, Go, JS, Python & more
License: unknown
Published: 4 days ago

Publisher: BaiduComate


SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
2 debugging symbols found

Security

Vulnerabilities
1 critical severity vulnerabilities
Hardening
1 reduced effectiveness mitigations

Threats

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

Popularity

309.5k
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

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

64 packages
found in
Top 100
445 packages
found in
Top 1k
2064 packages
found in
Top 10k
9214 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.

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

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. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in Visual Studio Code community

12 packages
found in
Top 100
62 packages
found in
Top 1k
231 packages
found in
Top 10k
638 packages
in community

Next 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.

Problem

Stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. Older compilers might generate stack cookies in a way that makes it possible to determine their value, allowing the attacker to render the mitigation ineffective.

Prevalence in Visual Studio Code community

17 packages
found in
Top 100
98 packages
found in
Top 1k
146 packages
found in
Top 10k
542 packages
in community

Next steps

In GCC, you can enable the stack canary with -fstack-protector-strong or -fstack-protector-all flag, but it may also be enabled by default in more recent versions of the compiler.
Consider upgrading your compiler.

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

70 packages
found in
Top 100
531 packages
found in
Top 1k
3115 packages
found in
Top 10k
16606 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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community

Prevalence in Visual Studio Code community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
3 packages
found in
Top 100
26 packages
found in
Top 1k
64 packages
found in
Top 10k
359 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
85 packages
found in
Top 100
673 packages
found in
Top 1k
4329 packages
found in
Top 10k
28768 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
81 packages
found in
Top 100
631 packages
found in
Top 1k
3887 packages
found in
Top 10k
24357 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
73 packages
found in
Top 100
573 packages
found in
Top 1k
3170 packages
found in
Top 10k
17492 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(3 Active Vulnerabilities)
3 (2 Fixable)
CVE-2025-24964c
CVE-2024-21503m
CVE-2024-43796m
None
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated