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

azure-cli

Artifact:
Microsoft Azure Command-Line Tools
License: Permissive (MIT)
Published: 3 months ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 web service credentials found

Security

Vulnerabilities
1 high severity vulnerabilities
Hardening
No application hardening issues

Threats

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

INCIDENTS:

Popularity

256.52M
Total Downloads
Contributor
Declared Dependencies
79
Dependents

Top issues

Problem

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, web service users provide a unique token that confirms their access rights. These tokens are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

Prevalence in PyPI community

3 packages
found in
Top 100
12 packages
found in
Top 1k
77 packages
found in
Top 10k
2425 packages
in community

Next steps

You should securely store web service access tokens, and fully automate their management and periodic rotation.
If tokens were published unintentionally and the software has been made public, you should revoke exposed tokens and file a security incident.
Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.

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.

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.

Problem

Various network communication protocols allow including plaintext authentication credentials. Information such as user names and passwords could be passed through a non-encrypted channel, and therefore intercepted by malicious actors. Credentials are considered secrets, and should be kept encrypted until they are used. This policy control matches the following URI pattern protocol://username:password@domain within any software package component.

Prevalence in PyPI community

21 packages
found in
Top 100
85 packages
found in
Top 1k
369 packages
found in
Top 10k
6869 packages
in community

Next steps

Review the reported matches. If the warning refers to a placeholder credential value, it can be safely ignored.

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in PyPI community

0 packages
found in
Top 100
2 packages
found in
Top 1k
7 packages
found in
Top 10k
1009 packages
in community

Next steps

Investigate reported detections.
If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Top behaviors

Prevalence in PyPI community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
6 packages
found in
Top 1k
7 packages
found in
Top 10k
231 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
34 packages
found in
Top 100
185 packages
found in
Top 1k
1062 packages
found in
Top 10k
25867 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
13 packages
found in
Top 100
99 packages
found in
Top 1k
566 packages
found in
Top 10k
19246 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
9 packages
found in
Top 100
94 packages
found in
Top 1k
476 packages
found in
Top 10k
16117 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
8 packages
found in
Top 100
64 packages
found in
Top 1k
281 packages
found in
Top 10k
8972 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
1 (1 Fixable)
CVE-2018-1000805h
1 (1 Fixable)
CVE-2022-24302m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated