Spectra Assure

failIncident: Removal

Scanned:

tensorflow-aarch64

Artifact:

removed

License: unknown

Published:

See on PyPI

SAFE Assessment

Compliance

Licenses

1 weak copyleft linked components

Secrets

136 debugging symbols found

Security

Vulnerabilities

10 severe vulnerabilities exploited

Hardening

68 reduced effectiveness mitigations

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

IMPORTANT: This package had 78 removal incidents in the last 2 years

Latest removal incident detected:

Version: 2.12.0rc1

INCIDENTS FOR THIS VERSION:

removal

Reported By: Community

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

Policies

Info

Count

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

38 packages

found in

Top 100

303 packages

found in

Top 1k

2611 packages

found in

Top 10k

103184 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.

SQ31103

Detected presence of malware-exploited vulnerabilities.

Causes risk: malware exploited vulnerabilities

vulnerabilities

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.

Prevalence in PyPI community

10 packages

found in

Top 100

78 packages

found in

Top 1k

751 packages

found in

Top 10k

27887 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.

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

25 packages

found in

Top 100

212 packages

found in

Top 1k

1951 packages

found in

Top 10k

77976 packages

in community

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.

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

50 packages

found in

Top 100

352 packages

found in

Top 1k

2858 packages

found in

Top 10k

108771 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.

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

1 packages

found in

Top 100

13 packages

found in

Top 1k

76 packages

found in

Top 10k

1063 packages

in community

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.

SQ12405

Detected presence of licenses that place restrictions on software distribution.

Causes risk: software distribution restrictions

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. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in PyPI community

6 packages

found in

Top 100

50 packages

found in

Top 1k

737 packages

found in

Top 10k

99544 packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

SQ18109

Detected Linux executable files that use a deprecated method to store the security cookie, making the buffer overrun vulnerability mitigation protection less effective.

Causes risk: reduced effectiveness mitigations

hardening

Problem

Stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. Older compilers might generate stack cookies in a way that makes it possible to determine their value, allowing the attacker to render the mitigation ineffective.

Prevalence in PyPI community

15 packages

found in

Top 100

65 packages

found in

Top 1k

317 packages

found in

Top 10k

2535 packages

in community

Next steps

In GCC, you can enable the stack canary with -fstack-protector-strong or -fstack-protector-all flag, but it may also be enabled by default in more recent versions of the compiler.

Consider upgrading your compiler.

SQ31106

Detected presence of medium severity vulnerabilities.

Causes risk: medium 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 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.

TH16112

Detected presence of software components that can tamper with the system certificate stores.

hunting

Problem

Software components sometimes need to interact with higher privilege parts of the operating system, often requiring administrative access to accomplish a task. System certificate stores are databases that define the chain of trust for a machine. These databases control the list of websites the machine can securely connect to, and the list of applications that the operating system implicitly trusts. For that reason, attackers often abuse system certificate stores to ensure their malicious code executes without being detected by security solutions. While the presence of code that tampers with system certificate stores does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that interact with system certificate stores. One example of acceptable use for such functions is adding publisher certificates to the system trust store during software installation.

Prevalence in PyPI community

2 packages

found in

Top 100

7 packages

found in

Top 1k

28 packages

found in

Top 10k

343 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1553.004 - Install Root Certificate Subvert.

Consider rewriting the flagged code without using the marked behaviors.

TH17118

Detected presence of files containing URLs that use suspicious top-level domains.

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. Top-level domains (TLD) are a part of the Domain Name System (DNS), and are used to lookup an Internet Protocol (IP) address of a requested website. There are a few different types of top-level domains. Generic, sponsored and country-code TLDs are generally accessible to the public. Registrars that govern the assignment of domain names within the TLD may choose to sell specific domain names to an interested party. However, some registrars are known to have less strict rules for assigning domain names. Attackers often abuse gaps in governance and actively seek to register their malicious domains in such TLDs. This issue is raised for all domains registered within TLDs that harbor an excessive number of malicious sites. While the presence of suspicious TLDs does not imply malicious intent, all of its uses in a software package should be documented and approved.

Prevalence in PyPI community

12 packages

found in

Top 100

83 packages

found in

Top 1k

478 packages

found in

Top 10k

15910 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 top-level domain to avoid being flagged by security solutions.

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

38 packages

found in

Top 100

303 packages

found in

Top 1k

2611 packages

found in

Top 10k

103184 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.

SQ31103

Detected presence of malware-exploited vulnerabilities.

Causes risk: malware exploited vulnerabilities

vulnerabilities

Problem

Prevalence in PyPI community

10 packages

found in

Top 100

78 packages

found in

Top 1k

751 packages

found in

Top 10k

27887 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.

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

25 packages

found in

Top 100

212 packages

found in

Top 1k

1951 packages

found in

Top 10k

77976 packages

in community

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.

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

50 packages

found in

Top 100

352 packages

found in

Top 1k

2858 packages

found in

Top 10k

108771 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.

SQ12103

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

Causes risk: weak copyleft linked components

licenses

Problem

Prevalence in PyPI community

1 packages

found in

Top 100

13 packages

found in

Top 1k

76 packages

found in

Top 10k

1063 packages

in community

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.

SQ12405

Detected presence of licenses that place restrictions on software distribution.

Causes risk: software distribution restrictions

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. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in PyPI community

6 packages

found in

Top 100

50 packages

found in

Top 1k

737 packages

found in

Top 10k

99544 packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

SQ18109

Detected Linux executable files that use a deprecated method to store the security cookie, making the buffer overrun vulnerability mitigation protection less effective.

Causes risk: reduced effectiveness mitigations

hardening

Problem

Prevalence in PyPI community

15 packages

found in

Top 100

65 packages

found in

Top 1k

317 packages

found in

Top 10k

2535 packages

in community

Next steps

In GCC, you can enable the stack canary with -fstack-protector-strong or -fstack-protector-all flag, but it may also be enabled by default in more recent versions of the compiler.

Consider upgrading your compiler.

SQ31106

Detected presence of medium severity vulnerabilities.

Causes risk: medium 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 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.

TH16112

Detected presence of software components that can tamper with the system certificate stores.

hunting

Problem

Prevalence in PyPI community

2 packages

found in

Top 100

7 packages

found in

Top 1k

28 packages

found in

Top 10k

343 packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1553.004 - Install Root Certificate Subvert.

Consider rewriting the flagged code without using the marked behaviors.

TH17118

Detected presence of files containing URLs that use suspicious top-level domains.

hunting

Problem

Prevalence in PyPI community

12 packages

found in

Top 100

83 packages

found in

Top 1k

478 packages

found in

Top 10k

15910 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 top-level domain to avoid being flagged by security solutions.