Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 4 days ago

Genesis Code

Artifact:
latest
Top 10k
Sega genesis Development Extension
License: unknown
Published: 9 months ago

Publisher: zerasul



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

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

Popularity

10.73k
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

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.

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.

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

25 packages
found in
Top 100
151 packages
found in
Top 1k
793 packages
found in
Top 10k
3.71k 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

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.

Top behaviors

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

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

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

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

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

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2022-25851h
CVE-2020-8175m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated