Spectra Assure
Community
Docs
warningRisk: Hardening
Scanned: 20 days ago

vscode-pets

Artifact:
latest
Top 1k
Pets for your VS Code
License: Permissive (MIT)
Published: about 1 month ago

Publisher: tonybaloney



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
1 baseline mitigations missing

Threats

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

Popularity

2.04M
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

Problem

ASLR (address-space layout randomization) is a mitigation technique that increases the difficulty of performing buffer-overflow attacks that require the attacker to know the address of the program in memory. This is done by loading the program at a randomly selected address in the process' address space. ASLR-enabled kernels can choose a random load address only for position-independent executables and code.

Prevalence in Visual Studio Code community

25 packages
found in
Top 100
144 packages
found in
Top 1k
407 packages
found in
Top 10k
1385 packages
in community

Next steps

To support ASLR, the program must be compiled as position-independent code. In most compilers, this is done by passing the corresponding position-independent flag, such as -fPIC for shared libraries or -fPIE for executables.

Problem

On Linux, external symbols are resolved via the procedure linkage table (PLT) and the global offset table (GOT). Without any protection, both are writable at runtime and thus leave the executable vulnerable to pointer hijacking - an attack where the function address is overwritten with an address of a malicious function. Pointer hijacking can be mitigated by using full read-only relocations, which instruct the compiler to unify global offset tables into a single read-only table. This requires that all external function symbols are resolved at load-time instead of during execution, and may increase loading time for large programs.

Prevalence in Visual Studio Code community

31 packages
found in
Top 100
208 packages
found in
Top 1k
641 packages
found in
Top 10k
2515 packages
in community

Next steps

In most cases, it's recommended to use full read-only relocations (in GCC: -Wl,-z,relro,-z,now).
If the executable load-time is an issue, you should use partial read-only relocations.

Problem

Proprietary ReversingLabs analysis engine supports a wide range of commonly used archive and software packaging formats. Using automated static file decomposition technologies, the engine recursively analyzes complex software packages. Software analysis is typically conducted in multiple steps. Content identification, unpacking, validation, and classification are some of the steps performed on each analyzed file. The analysis engine may sometimes identify archive or software packaging formats that are not supported for deep file inspection or unpacking. This issue is reported for files that might contain additional software components that were not listed in the Software Bill of Materials (SBOM) due to lack of packaging format support. File reputation lookup and surface level analysis are still performed for all unsupported file formats. Therefore, some files might get detected as malicious even though they are packaged in an unsupported format.

Prevalence in Visual Studio Code community

1 packages
found in
Top 100
7 packages
found in
Top 1k
21 packages
found in
Top 10k
73 packages
in community

Next steps

Consult the ReversingLabs product documentation for a list of supported archive and software packaging formats.
Consider repackaging the software in an alternative file format to increase the analysis coverage.
Contact the ReversingLabs product management team to discuss our format coverage roadmap.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
834 packages
found in
Top 1k
6690 packages
found in
Top 10k
83799 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
47 packages
found in
Top 100
282 packages
found in
Top 1k
936 packages
found in
Top 10k
4064 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
51 packages
found in
Top 100
365 packages
found in
Top 1k
1242 packages
found in
Top 10k
5691 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
79 packages
found in
Top 100
552 packages
found in
Top 1k
2856 packages
found in
Top 10k
16865 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
88 packages
found in
Top 100
709 packages
found in
Top 1k
4291 packages
found in
Top 10k
27290 packages
in community

Top vulnerabilities

No vulnerabilities found.