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

Amiga C/C++ Compile, Debug & Profile (Architect fork)

Artifact:
latest
Top 10k
One-stop VS Code Extension to compile, debug and profile Amiga C/C++ programs compiled by the bundled gcc 12.1 with the bundled WinUAE (Windows only)
License: Copyleft (GPL-3.0-or-later)
Published: almost 3 years ago

Publisher: davidcanadasmazo



SAFE Assessment

Compliance

Licenses
1 copyleft licensed components
Secrets
1 debugging symbols found

Security

Vulnerabilities
25 severe vulnerabilities exploited
Hardening
12 baseline mitigations missing

Threats

Tampering
1 components with malware history
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

17.86k
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

71 packages
found in
Top 100
568 packages
found in
Top 1k
3198 packages
found in
Top 10k
16595 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 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

Data Execution Prevention (DEP/NX) is a vulnerability mitigation option that prevents data from being interpreted as code anywhere within the application. This mitigation protects the application stack, heap and other memory data ranges. Executable files that fail to implement this mitigation expose the user to increased risks of malicious code injection.

Prevalence in Visual Studio Code community

10 packages
found in
Top 100
83 packages
found in
Top 1k
299 packages
found in
Top 10k
1003 packages
in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.
To enable this mitigation, refer to your programming language linker documentation.
In Microsoft VisualStudio, you can enable DEP mitigation by setting the linker option /NXCOMPAT to ON.

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

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Imported function addresses are pointers to the symbols that implement the application-required functionality. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.

Prevalence in Visual Studio Code community

20 packages
found in
Top 100
156 packages
found in
Top 1k
474 packages
found in
Top 10k
1793 packages
in community

Next steps

Review the programming language linker options, and consider a build toolchain update.

Top behaviors

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 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 often found in this community (Common)
26 packages
found in
Top 100
152 packages
found in
Top 1k
335 packages
found in
Top 10k
1452 packages
in community

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
3 packages
found in
Top 1k
26 packages
found in
Top 10k
94 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(70 Active Vulnerabilities)
11 (11 Fixable)
CVE-2016-9533c
CVE-2016-9535c
CVE-2013-1961c
59 (59 Fixable)
CVE-2016-9534c
CVE-2016-9841c
CVE-2016-9843c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated