failIncident: Removal

Scanned:

Azure.Storage

Microsoft Azure PowerShell - Storage service cmdlets. Manages blobs, queues, tables and files in Microsoft Azure storage accounts

License: unknown

Published:

Visit GitHub

See on PowerShell Gallery

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

6 debugging symbols found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal

N/AReported By: Community

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

Policies

Info

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 PowerShell Gallery community

7 packages

found in

Top 100

387 packages

found in

Top 1k

1476 packages

found in

Top 10k

2.58k 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

Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.

Prevalence in PowerShell Gallery community

3 packages

found in

Top 100

106 packages

found in

Top 1k

237 packages

found in

Top 10k

424 packages

in community

Next steps

Remove private debug database files from the software package before you release it.

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.

Prevalence in PowerShell Gallery community

87 packages

found in

Top 100

354 packages

found in

Top 1k

1060 packages

found in

Top 10k

1.69k packages

in community

Next steps

Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.

With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

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 PowerShell Gallery community

13 packages

found in

Top 100

124 packages

found in

Top 1k

643 packages

found in

Top 10k

1.03k 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.

Problem

Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.

Prevalence in PowerShell Gallery community

5 packages

found in

Top 100

123 packages

found in

Top 1k

371 packages

found in

Top 10k

631 packages

in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.

If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

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.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

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

Policies

Info

Problem

Prevalence in PowerShell Gallery community

7 packages

found in

Top 100

387 packages

found in

Top 1k

1476 packages

found in

Top 10k

2.58k 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

Prevalence in PowerShell Gallery community

3 packages

found in

Top 100

106 packages

found in

Top 1k

237 packages

found in

Top 10k

424 packages

in community

Next steps

Remove private debug database files from the software package before you release it.

Problem

Prevalence in PowerShell Gallery community

87 packages

found in

Top 100

354 packages

found in

Top 1k

1060 packages

found in

Top 10k

1.69k packages

in community

Next steps

With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

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 PowerShell Gallery community

13 packages

found in

Top 100

124 packages

found in

Top 1k

643 packages

found in

Top 10k

1.03k 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.

Problem

Prevalence in PowerShell Gallery community

5 packages

found in

Top 100

123 packages

found in

Top 1k

371 packages

found in

Top 10k

631 packages

in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.

If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

Azure.Storage

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 1 removal incident in versions published within 2 years prior to the latestLatest version with removal incident detected: over 8 years agoVersion: 3.3.0

INCIDENTS FOR THIS VERSION:

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ34202Detected presence of private debug database files.Causes risk: debugging symbols foundsecrets

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ20119Detected digital signatures that rely on a weak digest algorithm for integrity validation.signatures

Problem

Prevalence in PowerShell Gallery community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ34101Detected presence of commonly distributed sensitive data.secrets

Problem

Prevalence in PowerShell Gallery community

Next steps

Did you know...

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ34202Detected presence of private debug database files.Causes risk: debugging symbols foundsecrets

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ20119Detected digital signatures that rely on a weak digest algorithm for integrity validation.signatures

Problem

Prevalence in PowerShell Gallery community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in PowerShell Gallery community

Next steps

SQ34101Detected presence of commonly distributed sensitive data.secrets

Problem

Prevalence in PowerShell Gallery community

Next steps