Spectra Assure
Community
Docs
failIncident: Removal
Scanned: 12 days ago

redisvl

Artifact:
Python client library and CLI for using Redis as a vector database
License: Permissive (MIT)
Published: 8 months ago




SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 medium severity vulnerabilities
Hardening
No application hardening issues

Threats

Tampering
1 components prone to hijacking
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal
Reported By: Community

Popularity

3.23M
Total Downloads
Contributor
Declared Dependencies
29
Dependents

Top issues

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 PyPI community

33 packages
found in
Top 100
206 packages
found in
Top 1k
1631 packages
found in
Top 10k
63840 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 an alternative delivery mechanism for software packages.

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. Software developers publish components they have authored to public repositories. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in PyPI community

No prevalence information at this time

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

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 PyPI community

48 packages
found in
Top 100
311 packages
found in
Top 1k
2806 packages
found in
Top 10k
142146 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.

Top behaviors

Prevalence in PyPI community

Behavior often found in this community (Common)
5 packages
found in
Top 100
28 packages
found in
Top 1k
165 packages
found in
Top 10k
3060 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
5 packages
found in
Top 100
28 packages
found in
Top 1k
162 packages
found in
Top 10k
3073 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
33 packages
found in
Top 100
207 packages
found in
Top 1k
1634 packages
found in
Top 10k
63910 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
6 packages
found in
Top 100
38 packages
found in
Top 1k
219 packages
found in
Top 10k
4833 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
8 packages
found in
Top 100
36 packages
found in
Top 1k
229 packages
found in
Top 10k
4476 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(1 Active Vulnerabilities)
1 (1 Fixable)
CVE-2024-3772m
None
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated