Spectra Assure

warningRisk: Hardening

Scanned:

Language Support for Java(TM) by Red Hat

Artifact:

latest

key project

Top 100

Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more...

License: Copyleft (EPL-2.0)

Published:

Publisher: redhat

Visit Github

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

1 weak copyleft linked components

Secrets

43 debugging symbols found

Security

Vulnerabilities

2 medium severity vulnerabilities

Hardening

10 baseline mitigations missing

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

IMPORTANT: This package had 1 malicious incident in the last 2 years

Latest malware incident detected:

Version: 1.13.2022111803

INCIDENTS:

List of software quality issues with the number of affected components.

Policies

Info

Count

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

No prevalence information at this time

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.

SQ14140

Detected Windows executable files compiled without following the SDL best practices while using banned string functions.

Causes risk: misconfigured toolchains detected

hardening

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

No prevalence information at this time

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.

SQ14156

Detected Windows executable files with imported functions susceptible to pointer hijacking.

Causes risk: execution hijacking concerns

hardening

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

No prevalence information at this time

Next steps

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

SQ14158

Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.

Causes risk: execution hijacking concerns

hardening

Problem

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Thread local storage (TLS) callbacks are pointers to code initialization and resource release functions. 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

No prevalence information at this time

Next steps

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

SQ18101

Detected Linux executable files that declare the stack as executable, making non-executable memory mitigations less effective.

Causes risk: baseline mitigations missing

hardening

Problem

The stack is a special program segment which is writable by design, and is commonly used to store function-specific data and execution context. Granting execution privileges to the stack segment reduces application security, because it makes it possible to execute arbitrary code stored on the stack. While many modern compilers will implement a non-executable stack by default, it can be unintentionally disabled or made explicitly executable in automatically generated or misconfigured compiler options.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Enable non-executable stack mitigation with the -z noexecstack parameter during compilation.

TH17127

Detected presence of files containing URLs that link to raw files on GitHub.

hunting

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

No prevalence information at this time

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.

TH17131

Detected presence of files containing domains used for intercepting and inspecting HTTP requests.

hunting

Problem

Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.

Prevalence in Visual Studio Code community

No prevalence information at this time

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 removing all references to flagged network locations.

TH18101

Detected presence of files containing URLs that reside in regions with US export restrictions.

hunting

Problem

Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The United States Government has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Cuba (.cu), Iran (.ir), North Korea (.nk) and Syria (.sy).

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

You should delay the software release until the legal review is completed.

TH18102

Detected presence of files containing URLs that reside in regions with EU export restrictions.

hunting

Problem

Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The European Union has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Belarus (.by), Iran (.ir), Iraq (.iq), Libya (.ly), Myanmar (.mm), North Korea (.nk), Syria (.sy), Venezuela (.ve) and Zimbabwe (.zw).

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

You should delay the software release until the legal review is completed.

SQ12103

Detected presence of statically linked dependencies distributed with weak copyleft licenses.

Causes risk: weak copyleft linked components

licenses

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Weak copyleft licenses in particular impose requirements that the user must be able to replace or update the code they apply to. In practical terms, that means the object and library files that statically link to weak copyleft code must be made available publicly. For commercial applications, this is typically undesirable. Therefore, statically linking to weak copyleft code is commonly avoided or even prohibited by the organization policy. Instead of linking statically to weak copyleft licensed code, it is recommended to isolate such code into modules that the publisher-developed, first-party code can dynamically link to without the aforementioned obligations.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Confirm that the software package statically links to a weak copyleft dependency.

Investigate if the software publisher provides this dependency under a non-copyleft license.

Consider replacing the software dependency with an alternative that offers a license compatible with commercial use.

Alternatively, repackage the code so that it dynamically links to a weak copyleft dependency.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

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.

SQ14140

Detected Windows executable files compiled without following the SDL best practices while using banned string functions.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

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.

SQ14156

Detected Windows executable files with imported functions susceptible to pointer hijacking.

Causes risk: execution hijacking concerns

hardening

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

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

SQ14158

Detected Windows executable files with TLS callbacks susceptible to pointer hijacking.

Causes risk: execution hijacking concerns

hardening

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

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

SQ18101

Detected Linux executable files that declare the stack as executable, making non-executable memory mitigations less effective.

Causes risk: baseline mitigations missing

hardening

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Enable non-executable stack mitigation with the -z noexecstack parameter during compilation.

TH17127

Detected presence of files containing URLs that link to raw files on GitHub.

hunting

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

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.

TH17131

Detected presence of files containing domains used for intercepting and inspecting HTTP requests.

hunting

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

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 removing all references to flagged network locations.

TH18101

Detected presence of files containing URLs that reside in regions with US export restrictions.

hunting

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

You should delay the software release until the legal review is completed.

TH18102

Detected presence of files containing URLs that reside in regions with EU export restrictions.

hunting

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

You should delay the software release until the legal review is completed.

SQ12103

Detected presence of statically linked dependencies distributed with weak copyleft licenses.

Causes risk: weak copyleft linked components

licenses

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Confirm that the software package statically links to a weak copyleft dependency.

Investigate if the software publisher provides this dependency under a non-copyleft license.

Consider replacing the software dependency with an alternative that offers a license compatible with commercial use.

Alternatively, repackage the code so that it dynamically links to a weak copyleft dependency.