Spectra Assure
Community
Docs
failRisk: Vulnerabilities
Scanned: about 1 month ago

REST Client

Artifact:
latest
key project
Top 1k
REST Client for Visual Studio Code
License: Permissive (MIT)
Published: about 3 years ago
Publisher: humao
Visit Github
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
4 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

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

Popularity

6.43M
Total Installs
1
Contributor
27
Declared Dependencies
25
Dependents

Top issues

See all 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

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.

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.

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.

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.

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

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.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(8 Active Vulnerabilities)
3 (1 Fixable)
CVE-2022-37616c
CVE-2021-32796m
CVE-2022-33987m
5 (4 Fixable)
CVE-2022-39353c
CVE-2023-26136c
CVE-2024-21534c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for REST Client

What is REST Client?

REST Client for Visual Studio Code. For more information about this package, visit its homepage.

Is REST Client malicious or is it safe to use?

The VS Code package REST Client was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is REST Client popular?

The VS Code package REST Client is classified as a key project because of its widespread usage and impact. REST Client ranks among the top 1000 projects in the VS Code community. It has 6M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure REST Client once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how REST Client behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a REST Client version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

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.