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

Docker Explorer

Artifact:
latest
Top 1k
Manage Docker Containers, Docker Images, Docker Hub and Azure Container Registry
License: Permissive (MIT)
Published: almost 6 years ago
Publisher: formulahendry
Visit Github
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
5 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

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

Popularity

1.09M
Total Installs
1
Contributor
2
Declared Dependencies
4
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

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 high severity.

Prevalence in Visual Studio Code community

72 packages
found in
Top 100
583 packages
found in
Top 1k
3344 packages
found in
Top 10k
17282 packages
in community

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.

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

70 packages
found in
Top 100
531 packages
found in
Top 1k
3115 packages
found in
Top 10k
16606 packages
in community

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.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in Visual Studio Code community

57 packages
found in
Top 100
447 packages
found in
Top 1k
3421 packages
found in
Top 10k
56684 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

78 packages
found in
Top 100
551 packages
found in
Top 1k
2844 packages
found in
Top 10k
16607 packages
in community

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 changing the port to one that is standard for the networking protocol.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
81 packages
found in
Top 100
631 packages
found in
Top 1k
3887 packages
found in
Top 10k
24357 packages
in community

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)
62 packages
found in
Top 100
474 packages
found in
Top 1k
2491 packages
found in
Top 10k
12771 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
67 packages
found in
Top 100
493 packages
found in
Top 1k
2879 packages
found in
Top 10k
17817 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
50 packages
found in
Top 100
350 packages
found in
Top 1k
1388 packages
found in
Top 10k
6132 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(13 Active Vulnerabilities)
4 (4 Fixable)
CVE-2017-20165h
CVE-2024-28849m
CVE-2022-0536m
9 (9 Fixable)
CVE-2025-27152h
CVE-2019-10742h
CVE-2021-3749h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Docker Explorer

What is Docker Explorer?

Manage Docker Containers, Docker Images, Docker Hub and Azure Container Registry. For more information about this package, visit its homepage.

Is Docker Explorer malicious or is it safe to use?

The VS Code package Docker Explorer 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 Docker Explorer popular?

The VS Code package Docker Explorer ranks among the top 1000 projects in this community. It has 1M 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 Docker Explorer once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Docker Explorer behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Docker Explorer 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.