C# Dev Kit@1.73.8 - Visual Studio Code | ReversingLabs Spectra Assure Community

Popularity

11.85M

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

SQ31102

Detected presence of severe vulnerabilities with active exploitation.

Causes risk: actively exploited vulnerabilities

vulnerabilities

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

No prevalence information at this time

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.

SQ31104

Detected presence of critical severity vulnerabilities.

Causes risk: critical severity vulnerabilities

vulnerabilities

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

No prevalence information at this time

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.

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.

SQ31105

Detected presence of high severity vulnerabilities.

Causes risk: high severity vulnerabilities

vulnerabilities

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

No prevalence information at this time

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.

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.

Top behaviors

See all behaviors

Contains potentially deceptive links.

evasion